select2 also shows icons not included in kit subset

  • Resolved Jules Colle

    (@jules-colle)


    6 months, 4 weeks ago

    Hi Matt

    I’m using your development version of the plugin.

    In our fontawesome kit we have created a subset of solid icons. The problem is that all solid icons are shown in the dropdown, but only some should be available. It’s not a super big problem because it’s obvious which icons are available or not, but it would be nice if the list would only show the icons that we actually support.

    If there’s a solution that involves writing some code, that’s also fine ??

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Matt Keys

    (@mattkeys)

    Hey @jules-colle thanks for the testing and question.

    Last I checked, the FontAwesome GraphQL API search that is used by this plugin does not support limiting itself to search only within the subset defined in the kit.

    This is something I had mentioned to the FontAwesome team about 10 months ago and they understood how it would be needed/useful here.

    I’ll try and check back in with them and see if this is on the roadmap or not. I am sure they have all been very busy with their Web Awesome kickstarter so I’m not sure if I’ll hear back right away. But I’ll share what I learn here when I do.

    Plugin Author Matt Keys

    (@mattkeys)

    I should add that in the meantime, as a work around, there is a similar subsetting feature available in this plugin.

    Check out the ‘icon set builder’ in the plugin settings area. This will be a bit redundant once the GraphQL subsetting search is working, but I developed this for this plugin a long time ago.

    Thread Starter Jules Colle

    (@jules-colle)

    Thanks for the great support. We’ll leave it like this for now

    Plugin Author Matt Keys

    (@mattkeys)

    Just an FYI, I have been chatting with FontAwesome about this. I don’t have an ETA but it is something that is being thought about/is on the road map.

    Thread Starter Jules Colle

    (@jules-colle)

    Thanks for the info! We have currently decided on another approach that allows us to use the pro kit with a bit of extra hassle. We download the icons all as svgs and add them to our repo. By creating a custom acf field that reads the directory our users can then select the icons. We miss the nice search feature because of this, but at least we don’t have an endless list of unsupported icons now

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.