-
Notifications
You must be signed in to change notification settings - Fork 830
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
Rename some wrongly named icons #1023
base: main
Are you sure you want to change the base?
Conversation
We have other icons like `circle` and `circle-slash`. In Figma these icons are also called `circle-check`. It feels wrong to invert the naming logic for this one icon.
|
Hi! This pull request has been marked as stale because it has been open with no activity for 60 days. You can comment on the pull request or remove the stale label to keep it open. If you do nothing, this pull request will be closed in 7 days. |
@camertron, pinging you as I hope you can help. We are currently in a tough spot, were renaming icons is nearly impossible, as we need to update the entire consuming project at the same time. I think we need an approach that allows us to deprecate icons but keep them in package somehow. Basically, having two versions of an icon, but one comes from a deprecated folder? I don't know if we can log a console message for deprecated icons, e.g. `The icon "iconName-16" is deprecated, please use "newIconName-16" instead. This would allow us to have both versions in the package at the same time, so that we can update the consumers and remove the icons in a next major. Any thoughts? |
We have other icons like
circle
andcircle-slash
. In Figma these icons are also calledcircle-check
. It feels wrong to invert the naming logic for this one icon.The alternative would be to go the other way and rename the remaining icons and all figma icons to
[thing]-circle
.Warning
Warning: This is probably a breaking change. We could mitigate this by: