We need to figure out how we handle breaking changes to icons, namely:
1. Renaming an icon
Should name changes be handled solely by consumers, or should we provide any direct support (other than efficiently communicating the changes)?
Should consumers create aliases or any other sort of fallback? The problem with aliases for backward compatibility is that those could clash with future icons that may need to reuse the deprecated name.
2. Deleting an icon
The icon is no longer available. Should it be removed from the codebase right away, or should it be marked somehow as deprecated?
Existing instances need to be replaced by an alternative icon.
All other changes to icons are considered non-breaking and require no extra coordination overhead:
3. Adding a new icon — New icons will be picked up by the scripts we use to generate the icon assets from Figma.
4. Updating the design for an icon — Iterating on an icon design should be cost-free from the implementation side. Other than regularly syncing the icons from Figma to GitHub, there shouldn't be extra work involved.
Tasks:
[ ] Decide on how to handle scenarios 1. and 2., involving engineers from each platform on the discussion.
We need to figure out how we handle breaking changes to icons, namely:
1. Renaming an icon
2. Deleting an icon
All other changes to icons are considered non-breaking and require no extra coordination overhead:
Tasks: