-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Part of #18714: Replacing deprecated constants in Icon
folder
#19250
Conversation
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
Codecov Report
@@ Coverage Diff @@
## develop #19250 +/- ##
===========================================
- Coverage 70.36% 70.36% -0.01%
===========================================
Files 961 961
Lines 36850 36850
Branches 9589 9589
===========================================
- Hits 25929 25927 -2
- Misses 10921 10923 +2
|
hi @georgewrmarshall , could you please review this PR when possible? |
@dhruvv173 when you get a chance fix that conflict, otherwise this is looking good |
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.
Hey @dhruvv173, this is looking good I did a search for the deprecated consts inside of the icon folder and got a result on FLEX_DIRECTION
that needs updating. You will also need to resolve the conflict as @garrettbear mentioned
@garrettbear @georgewrmarshall |
hey @garrettbear @georgewrmarshall |
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! Thanks for your contribution @dhruvv173!
Explanation
Replaced deprecated design system and storybook constants in the
Icon
folderui/components/component-library/icon
Screenshots/Screencaps
Before
before.1.mp4
After
after.mp4
Manual Testing Steps
jest
testsPre-merge author checklist
Pre-merge reviewer checklist
If further QA is required (e.g. new feature, complex testing steps, large refactor), add the
Extension QA Board
label.In this case, a QA Engineer approval will be be required.