-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added “data-variant” attribute to components #407
base: main
Are you sure you want to change the base?
Added “data-variant” attribute to components #407
Conversation
…at property to <a> and <button> tag; - Added "data-variant" attribute to Flux free component, when possible;
I was just going to suggest this! Excellent! |
Very very useful change, thank you, can't wait to see it implemented! |
Would be very happy with this new feature. To be consistent, it could have the badge color names. |
Theoretically, this approach should be taken with all components that have a variant. Also in Pro version. |
@calebporzio have you thought about this? In a project I have a button that opens a modal with reports.
|
In my understanding it would also be the only way to easily add a layer of color customization to the buttons? |
Please @calebporzio can you consider adding attribute variant to the DOM so we can customize the colors more granularly ? |
Can't we use TailwindCSS 4.0 when it's stable to customize the color scheme via theme variables? What if the CSS classes are named for example @theme {
--color-primary-100: oklch(0.99 0 0);
--color-primary-200: oklch(0.98 0.04 113.22);
--color-primary-300: oklch(0.94 0.11 115.03);
...
} Or, use CSS variables / arbitrary values instead. |
Hello everyone!!!
I posted this PR that adds the
data-variant
attribute to Flux (free) components.This PR solves the [#393] discussion that I had started a couple of days ago..
The problem
I found myself in a situation where I had to apply a style to buttons (selectable via the
data-flux-button
attribute), but this style was being applied globally without distinction of the button variant.So the idea was to add, where possible, a
data-variant
attribute that could come in handy in case you want to apply a certain style only to certain variants and not to all of them.Video example
data-variant.example.mov
Code
<flux:button variant="primary" class="teal">Primary</flux:button>
<flux:button variant="outline" class="teal">Outline</flux:button>
[data-flux-button][data-variant="primary"].teal { @apply !bg-teal-500 !text-white hover:!bg-teal-400; }
[data-flux-button][data-variant="outline"].teal { @apply !bg-transparent !border-teal-500 !text-teal-500 hover:!border-teal-400; }
I'm excited to hear your thoughts!! What do you think? Can it be useful?
Thank you so much for the incredible work you do!!!
Regards,
Fabio