Skip to content

Conversation

@byronogis
Copy link

πŸ”— Linked issue

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

See https://tailwindcss.com/docs/v4-beta#using-a-prefix

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

TODO: dynamic content in css file
Example
- origin value (from button tv):  variants.size.md..leadingAvatarSize: '2xs'
- appConfig value: appConfig.ui.button.variants.size.md.leadingAvataSize: 'md
while get wrong size value ('2xs md') in avatar component
@byronogis byronogis changed the title Feat/support tailwind prefix Feat/support tailwind prefix in v3 Jan 3, 2025
@benjamincanac
Copy link
Member

I'm really sorry I've never taken the time to review your PR but there was too much complexity to handle this.

Closing this as the branch is really old with lots of conflicts and we're now on v4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

v3 #1289

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants