Respect Font Awesome Icons partial file configuration

Created on 20 August 2024, 8 months ago

Updated 21 August 2024, 8 months ago

Problem/Motivation

Font Awesome documentation says we can opt to specify styles (solid, brands, regular, etc). This is especially useful to us because we can use it to limit which icons we support.

Font Awesome Icons → offers the option of choosing which partial file configurations will be used to limit the icons loaded.

Font Awesome Iconpicker → does not limit the available icons based on the selected styles.

Steps to reproduce

Follow this module's instructions to enable, add a text field, and configure the widget.
Go to Configuration > Content authoring > Font Awesome Settings and limit to just the Solid (Free) style.
Create or Edit a node with this field, and activate the icon picker modal.

You will still see Brand icons in the list.

Proposed resolution

Font Awesome Iconpicker → says it fully supports integration with Font Awesome Icons → . The configuration noted above limits the icons loaded into the system. Font Awesome Iconpicker should respect that configured limit.

🐛 Bug report

Status

Active

Version

3.0

Component

User interface

Created by

🇺🇸United States jcandan

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @jcandan
Comment 8 months ago →
🇺🇸United States jcandan
So far as I can see on a cursory review, the set of Icons determined to be available are hard-coded here and here (Not sure why it is listed twice, and each list is different).

I imagine we could refactor this to a single place. Then ensure that place gets the list from configuration. There may also probably need to be a mapping from the above configuration to the iconSource options listed at the vanila-icon-picker NPM package docs.
Assigned to D34dMan
Comment 8 months ago →
🇩🇪Germany D34dMan Hamburg

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024