-
Notifications
You must be signed in to change notification settings - Fork 598
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
Button API alignment #2714
Button API alignment #2714
Conversation
🦋 Changeset detectedLatest commit: 674e54d The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
size-limit report 📦
|
…into button-api-alignment
Hey @langermank! I've been trying to make sure all the branches are up-to-date with the new vrt workflow. I wanted to ask if you have any free time this week to update the conflicts on this PR? |
@joshblack thanks for the reminder! I'm waiting for this PR that @broccolinisoup is working with me on to land before I update this PR since I think it will resolve a lot of the conflicts here. I had to revert the original PR that this PR is based on. |
Will reopen once #2792 merges |
Note to self: add these changes to this PR d79fbfc |
This PR includes breaking changes to bring the PRC Button up to the agreed upon API spec and match implementation with PVC.
leadingIcon
andtrailingIcon
toleadingVisual
andtrailingVisual
(a pattern introduced with ActionList)Button.Counter
as a child component, replacing it with atrailingVisualCount
prop. This change allows us to use thetrailingVisual
slot for counters, and also aligns better with all the other child elements within Button (visuals are props, not child components in this case.)outline
button variant as we wish to only supportinvisible
buttons.Screenshots
The only visual change is that the
outline
button variant has been removed.Merge checklist