glyphflow renamed its public surface in v2. The old names still work — this page says what changed, and until when.
What v2 changed
One thing: the prefix. Everything called Max* is now Gf*, and the elements <max-icon> / <max-icon-morph> are <gf-icon> / <gf-icon-morph>. The package is called glyphflow, so the brand is one word, not two. No behaviour changed with the rename.
The equivalence table
Every row on the left still resolves to the one on the right — they are the same object, not a copy. That matters for GF_ICONS_CONFIG in particular: two distinct injection tokens would not see each other, and a provideMaxIcons() would silently never reach the component.
| v1 | v2 |
|---|---|
<max-icon> | <gf-icon> |
<max-icon-morph> | <gf-icon-morph> |
MaxIconComponent | GfIconComponent |
MaxIconMorphComponent | GfIconMorphComponent |
provideMaxIcons | provideGfIcons |
MAX_ICONS_CONFIG | GF_ICONS_CONFIG |
MaxIconsConfig | GfIconsConfig |
How long the old names last
They are exported and marked @deprecated through the whole v2 line, and they go away in v3. Nothing breaks by upgrading to v2 — you can rename at your own pace.
A rename of a selector does not behave like a rename of a symbol: if a symbol disappears, TypeScript shouts. If a selector disappears, a template is just text — Angular treats the unknown element as nothing and renders it. Silently. That is why the old selectors stay.