No, this service registers the icons, it doesn't load any of them, until the view ultimately requests for one.
But yes, it registers all icons regardless if they are used or not.
and its quite easy to see that, if you create an interceptor and log all requests going through it, you will see requests on the svg files only when the view requests them.
What side effects does the registration have?
I am concerned about loading times and registration should not have a lot of impact to it. It feels somewhat wrong to register them globally and not only per lazy loaded module.
You can always create a method that registers icons on demand. Personally, I don't think you will gain much by doing that, apart from over complicating your solution.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
No, this service registers the icons, it doesn't load any of them, until the view ultimately requests for one.
But yes, it registers all icons regardless if they are used or not.
and its quite easy to see that, if you create an interceptor and log all requests going through it, you will see requests on the svg files only when the view requests them.
What side effects does the registration have?
I am concerned about loading times and registration should not have a lot of impact to it. It feels somewhat wrong to register them globally and not only per lazy loaded module.
I don't think there is match of an impact since the only thing that addSvgIcon does is add an entry on a Map Object.
github.com/angular/components/blob...
You can always create a method that registers icons on demand. Personally, I don't think you will gain much by doing that, apart from over complicating your solution.