Specifying icon prefix for icons added to library
See original GitHub issueIf an icon is added to the library with library.add(faUser)
, we can then display them in a template with <fa-icon="user"></fa-icon>
for solid icons. it looks like if we want to use the same icon from the “light” set, we would do <fa-icon icon="['fal', 'user']"></fa-icon>
.
Is this the intended syntax? It works, but is a bit clunky. It might be worth adding a separate “prefix” or “iconSet” input to handle those separately.
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
How To Add Icons | Font Awesome Docs
We've updated many of our icon names in Version 6 to make them more universal and consistent. But we wanted to make sure...
Read more >Cound not find icon react-fontawesome - Stack Overflow
You need to add any icons you wish to use, to a "library" for easy reference. import React from 'react'; import { render...
Read more >Icons Library in Blazor - Syncfusion
The font size of the icon can be changed using the Size property. The icon displays Medium size by default. ... The Size...
Read more >About Icons - Win32 apps | Microsoft Learn
Standard icons are predefined, so it is not necessary to create them. To use a standard icon, an application can obtain its handle...
Read more >How to create an icon library in Angular - Medium
SVG can be positioned by setting the size. Icon fonts on the ... Next, let's add the icons to an icons folder inside...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@karptonite yes, that was the same conclusion that we found with the vue-fontawesome component as well. There are advantages to the clunky 😒
Given our discussion above, I’m going to close this now, but glad to re-open if there’s more to explore here.