Yaroslav Admin

@Peco602 Please see [this comment](https://github.com/FortAwesome/angular-fontawesome/issues/48#issuecomment-432543956). You need to add the FA styles file to the global styles in your `angular.json`.

PR to improve documentation is welcome 😄 I think adding Accessibility article under [Guides](https://github.com/FortAwesome/angular-fontawesome/blob/master/docs/usage.md#guides) will be a good approach.

That's a valid point, but I don't think we can do much about it besides documenting it better. The thing is that this input sets classes **inside** the `fa-icon` component...

I'll re-open this issue as I want to write some documentation around this when I've got some time :)

Thanks for kind words @thepercival! In runtime world this *just works*. To support this feature in types world it is necessary to update type definitions for all FA packages ecosystem....

This issue is really about the type safety and auto-completion for custom icon names on the usage site, i.e. ``. If you're okey with some casts you can use custom...

Thanks for the info @jtinsley85. This is exactly what [I've been thinking about](https://github.com/devoto13/fa-icons-merge/blob/master/node_modules/%40fortawesome/free-regular-svg-icons/faAddressBook.d.ts#L12). Unfortunately such declarations are rather cumbersome. We only need icon name, but because declaration merging does not...

@lightman76 I think a `customIcon` binding is an interesting approach, but then we'll also need to add a `customMask` as `mask` binding takes icon as well. I'm somewhat hesitant about...

By default, the icon should match the font size of the place where it is added. I wonder why you need to change it? Can you describe your use case...

How do you envision it to work? My thinking is that with the limited maintainer time and given the small amount of breaking changes continuously maintaining multiple branches and backporting...