-
-
Notifications
You must be signed in to change notification settings - Fork 78.9k
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
Easier disabled state customization for button variants #30639
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's document this in our Migration guide (and explain it's new in alpha 2 somehow, I can work on that). Perhaps we also do some Sass references in the buttons docs?
fe3bac6
to
0faa9ea
Compare
I added a mention in the migration page, not sure about the wording but at least there's something, now :) Not sure about Sass reference in the buttons docs either, looks like a meta feature for all components—as requested several times, isn't it? |
Waiting to merge #31122 first so that we place all alpha2 changes in the new section. |
* feat(buttons): easier disabled state customization * docs(migration): mention new arguments for disabled state in button-variant() * Update migration.md Co-authored-by: XhmikosR <[email protected]> Co-authored-by: Mark Otto <[email protected]>
We can seamlessly ease the
disabled
state customization in thebutton-variant()
mixin by adding dedicated arguments, which default values are the previously used ones.I may have to mention this somewhere in the docs, if you're OK with the feature :)