- Issue created by @m4olivei
- Merge request !594Issue #3510801: Updates to use the core icon API override mechanism → (Open) created by m4olivei
- 🇨🇦Canada m4olivei Grimsby, ON
Now that 📌 Navigation leverage icon core API Needs work landed, this will be needed to override navigation icons as of 11.2.
I've added an MR to show what's needed. At a high level:
- Override the navigation icon pack (
gin.icons.yml
) - For all the icons that navigation provides, we need icons of the same name provided by Gin. This was the bulk of the adjustments necessary
- Override the navigation icon pack (
- 🇨🇭Switzerland saschaeggi Zurich
@m4olivei thanks for putting this together 👏
This is a promising start! As far as I can tell this currently would break Gin for all Drupal versions
Core < 11.2
We might want to keep the icons as-is as legacy to avoid breaking Gin. This can either be done
- Move CSS styles to the
legacy
CSS folder and ship it only forCore < 11.2
- We keep it as-is and ship the
gin.icons.yml
alongside the current method
- Move CSS styles to the
- 🇩🇪Germany jurgenhaas Gottmadingen
Yeah, for Gin 4.x we absolutely have to support the legacy way. We should use the same approach as for the project browser CSS library deprecation here as well.