-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Card
: support the extraSmall
option for the size
prop
#37097
Conversation
Size Change: +29 B (0%) Total Size: 1.11 MB
ℹ️ View Unchanged
|
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.
Looks good!
This looks great, thanks @ciampo! Adding the backport label as this is causing breakage on 5.9. |
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.
LGTM 👍
What's up with all the checks in this PR? Might need a rebase or something.
6b92c49
to
17f25d1
Compare
I rebased this to (hopefully) fix failing tests. |
* `Card`: support the `extraSmall` option for the `size` prop * Unit tests * CHANGELOG * Remove unnecessary markup from unit test
Description
As reported in #32566 (comment) , when the
Card
component was last updated, a change was introduced to the list of values accepted by thesize
prop.In particular, prior to that PR, the
Card
component was able to accept theextraSmall
value, while since that PR, it now accepts thexSmall
value instead.This PR introduces support for the legacy
extraSmall
value, avoiding a breaking change for the consumers of the component that are still using the older value.Note: the older
extraSmall
value is not mentioned in the README on purpose, in order to encourage folks to use the newerxSmall
value.How has this been tested?
extraSmall
as a potential value forsize
Types of changes
Fix
Checklist:
*.native.js
files for terms that need renaming or removal).