-
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
Deprecate duplicate icons #38849
Deprecate duplicate icons #38849
Conversation
I'm not sure who to best ping for review here, so I've gone with GitHub's suggestion on who touched the code last. Also for awareness, CC: @iamthomasbishop |
Size Change: +353 B (0%) Total Size: 1.15 MB
ℹ️ View Unchanged
|
/> | ||
</SVG> | ||
); | ||
|
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.
might be worth moving the sparkles icon module from the icons package into this package. sure it's fine having the SVG defined inline here, but it's obviously generated/optimized and so practically un-editable in place and so a bit awkward in the middle of another component.
not a big issue and some may disagree with me on this, but I think keeping it an import from another file would make it easier to think about and maintain. we wouldn't have to call it sparkles even; we could give it a semantic name like block-is-new-icon.svg
and then people would have the freedom to change it to something that isn't sparkles without changing the intent of the code/module/import.
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.
Thanks a bunch, that's much better. I took a stab at that in 499d4dc, hopefully I got the code right.
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.
Left a comment about organization and maintenance w.r.t. sparkles
but otherwise this looks benign and it's good to keep the icons in sync with the designs, so I don't see a compelling reason not to merge.
I'd really love some mobile eyes on this one before I land it. Thanks again for the review! |
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.
I checked the icon difference and looks great to me 👍 . Not sure if @iamthomasbishop has any concern about this change, it would be great to have that design input.
Before | After |
---|---|
![]() |
![]() |
Apart from this, I added a comment for fixing the sparkles icon import as it's required to display it.
@fluiddot @jasmussen The icon changes look good to me! |
Co-authored-by: Carlos Garcia <[email protected]>
Thanks a whole lot for all the reviews. I applied the suggestion! 👌 |
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 🎊 !
* Remove alignJustifyAlt. * Remove cogAlt. * Remove sparkles, trashFilled. * Move to imported sparkles icon. * Update packages/components/src/mobile/inserter-button/index.native.js Co-authored-by: Carlos Garcia <[email protected]>
Description
I've been doing some cleanup work on the Figma WordPress Design library, notably the Icons page, and have noticed it's out of sync with the icons that are present in Storybook.
Notably, it contains a couple of new icons that should not be there, as they are not designed for the new icon set. It's important we only add icons we need to that set, as they get published as a npm package. If we have to use a different icon we need a good reason, and then we can add those icons locally, so they don't get published as part of the package.
justifyAlt
is removed,justify
is used insteadcogAlt
is removed,cog
is used insteadsparkles
is moved to be a local icon instead of part of the packagetrashFilled
is removed,trash
is used instead.Types of changes
This is a breaking change for the node package, so I've updated the changelog.
I haven't been able to test this in the mobile emulator, so it should not be merged without a green check of someone who's able to do that.
Checklist:
*.native.js
files for terms that need renaming or removal).