Skip to content
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

refactor(button, fab, split-button)!: Update properties and values #6062

Merged
merged 4 commits into from
Dec 15, 2022

Conversation

macandcheese
Copy link
Contributor

@macandcheese macandcheese commented Dec 15, 2022

BREAKING CHANGE: Removed deprecated properties and values.

  • button: Removed the property form, this property is no longer needed if the component is placed inside a form.
  • button, fab, split-button: Renamed the property color, use kind instead.
  • button, fab, split-button: Updated the accepted values of kind to brand (default), danger, inverse, and neutral.
  • button, split-button: Updated the accepted values of appearance to outline, outline-fill and solid (default).
  • fab: Updated the accepted values of appearance to outline-fill and solid (default).

@macandcheese macandcheese added breaking change Issues and pull requests with code changes that are not backwards compatible. pr ready for visual snapshots Adding this label will run visual snapshot testing. labels Dec 15, 2022
@macandcheese macandcheese requested a review from a team as a code owner December 15, 2022 22:05
@github-actions github-actions bot added the refactor Issues tied to code that needs to be significantly reworked. label Dec 15, 2022
Copy link
Member

@driskull driskull left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@macandcheese code changes look good. Can we update the PR body to make the changes a little more clear?

Removed the button property form, this property is no longer needed if the component is placed inside a form.

At first glance, I wasn't sure if there was a property "button"? :)

@driskull
Copy link
Member

Maybe something like

CalciteButton: Removed the property form, this property is no longer needed if the component is placed inside a form.

BREAKING CHANGE: Removed deprecated properties and values.

- `button`: Removed the property `form`, this property is no longer needed if the component is placed inside a form.
- `button`, `fab`, `split-button`: Renamed the property `color`, use `kind` instead.
- `button`, `fab`, `split-button`: Updated the accepted values of `kind` to `brand` (default), `danger`, `inverse`, and `neutral`.
- `button`, `split-button`: Updated the accepted  values of `appearance` to  `outline`, `outline-fill` and `solid` (default).
- `fab`: Updated the accepted values of `appearance` to  `outline-fill` and `solid` (default).
@macandcheese macandcheese force-pushed the macandcheese/button-fab-split-button-refactor branch from 9be0095 to bcddc09 Compare December 15, 2022 22:30
@macandcheese macandcheese added pr ready for visual snapshots Adding this label will run visual snapshot testing. and removed pr ready for visual snapshots Adding this label will run visual snapshot testing. labels Dec 15, 2022
@macandcheese
Copy link
Contributor Author

@driskull want to give that new verbiage a look?

@SkyeSeitz @ashetland a couple of Chromatic changes to approve - reflecting to the change of default value for FAB appearance to solid

@driskull
Copy link
Member

Verbiage looks good! 👀 ❤️

@macandcheese macandcheese merged commit 969a2eb into master Dec 15, 2022
@macandcheese macandcheese deleted the macandcheese/button-fab-split-button-refactor branch December 15, 2022 23:22
@github-actions github-actions bot added this to the 2023 January Priorities milestone Dec 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change Issues and pull requests with code changes that are not backwards compatible. pr ready for visual snapshots Adding this label will run visual snapshot testing. refactor Issues tied to code that needs to be significantly reworked.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants