Repository navigation
[CupertinoIcons] move the font generation script and the codepoint map into the cupertino_icons repo/package #148075
Description
The contents of the cupertino_icons generation repo should be moved to flutter/packages
Per the comments here.
The generated dart file should be distributed as part of the cupertino_icons package
Currently the generated dart file is part of the cupertino library instead of the cupertino_icons package. With the font and the codepoint map living in different packages, there doesn't seem to be a way to properly version the dart codepoint binding, or to test it. Example: I would like to fix an incorrectly mapped codepoint in cupertino_icons < 1.08 but since the dart file lives in cupertino it would break code that's using older versions (https://github.com/flutter/flutter/pull/146806/files#diff-6622a57feb8a0b6d1674c2cad83821872010e3c8005be91079c3d34d466a0f91)
This could be a breaking change but not doing it is kinda bad too because we can't fix incorrect codepoints without breaking apps that are using older versions of cupertino_icons.
Activity
LongCatIsLooong commentedon May 9, 2024
Also consider removing the ligature table from the ttf and using codepoints in dartdoc, since users should be using the dart names instead of strings to refer to the icons, and the ligature names are not consistent with the dart names. This is relatively low priority.
10 remaining items
flutter-triage-bot commentedon Oct 30, 2024
This issue is assigned to @victorsanni but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!
flutter-triage-bot commentedon Jan 15, 2025
This issue was assigned to @victorsanni but has had no status updates in a long time. To remove any ambiguity about whether the issue is being worked on, the assignee was removed.
LongCatIsLooong commentedon May 13, 2026
It will be difficult for the CupertinoIcons package to keep up with new iOS icons updates (even from a pure technical perspective). Newer versions of SFSymbol have features like "Magical Replace" or "Variable Draw". Even if it's possible to replicate all these features in a regular open type variable font, it is going to require heavy investment (implementation and fidelity, and keeping up with new SFSymbol releases). The approach in this design doc seems much more sustainable.
Cupertino icons golden tests (flutter#7421)
Cupertino icons golden tests (flutter#7421)