icon parameter needs to be explicitly stated {{fa-icon icon='coffee'}}
See original GitHub issueI have followed the instructions to install this addon, however quickly notificed that {{fa-icon 'coffee'}}
only leads to a console message: ember-console.js:24 Could not find icon undefined
.
After checking the source I found that the only way that currently seems to work is to explicitly provide the icon parameter to the component like {{fa-icon icon='coffee'}}
. So either the docs or the addon currently seem to not work as intended.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
react-fontawesome importing all icons - Stack Overflow
Discussed this with the react-fa team and they advised that icons need to be explicitly imported with full paths:
Read more >A Simple Guide to Add FontAwesome in Angular
The explicit reference method entails importing the icon definition from the npm package, assigning it to the component's property, and binding this property...
Read more >How To Use Font Awesome icons in Angular Applications
We can use Font Awesome icons in Angular applications two ways depending upon our requirements. Using Explicitly in Component; Using Icon ...
Read more >What's New - Font Awesome
Every FA icon example page now has a better, more accessibility-minded ... We've added a new icon category specifically for accessibility and seeded...
Read more >Font Awesome 5 Vue component - BestofVue
If you have been using 0.1.x of vue-fontawesome, you c. ... Explicit icon definition through something like a computed property.
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 FreeTop 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
Top GitHub Comments
OK,
0.0.11
is now thelatest
Sorry, that’s probably because of the dist-tags. I’ve been pushing these prereleases with the
prerelease
tag. The last release that carried thelatest
tag (which is probably what you’re getting) was indeed0.0.10-1
.I think we’ve prereleased long enough for
0.0.11
. I’m going to push a real0.0.11
release that should clear this up for anyone in the future 😉