Feature Request: Support multiple paths for (custom) icons.

[Destreyf]

Describe the problem you'd like to see solved or task you'd like to see made easier

I am looking to use the fa-icon system to store my own SVG's as font awesome icons, these SVG's are multi-colored and thus have multiple paths, it'd be nice to be able to support multiple paths.

Is this in relation to an existing part of angular-fontawesome or something new?

I believe it would be super beneficial to support this behavior to support multi-colored icons.

What is 1 thing that we can do when building this feature that will guarantee that it is awesome?

It would allow multi-colored icons to be used by the community as well as provide a solid foundation for potential future icon packs to leverage the item system.

Why would other angular-fontawesome users care about this?

I believe the SVG icon approach is much more useful than having to reference/embed icons manually or maintain a separate set of components for the icons themselves.

On a scale of 1 (sometime in the future) to 10 (absolutely right now), how soon would you recommend we make this feature?

5 - I think it'd be super awesome but i understand that the uses within the community at this time are limited.

Feature request checklist

• This is a single feature (i.e. not a re-write of all of Font Awesome)
• The title starts with "Feature request: " and is followed by a clear feature name (Ex: Feature request: moar cowbell)
• I have searched for existing issues and to the best of my knowledge this is not a duplicate

[devoto13]

While it is not a complete solution new fa-duotone-icon component supports working with two paths.

[mjpoo]

Some handy info to add to @devoto13 's comment:

1. Multiple path strings can be provided in an array of as many strings as you like.
2. Only the first two strings will be used.

For others that stumble on this issue please note it is possible to use unlimited multiple paths in an IconDefinition by putting all your paths in the string. Of course you can't then style them separately like @Destreyf (and I) would like.