Hi santhosh raju!
Well the observable will re-subscribe when the component is recreated because the template will be re-evaluated and the | async pipe will teigger subscription.
In context of components, you don;t really want to re-subscribe because the component was usually destroyed.
Hi Vladimir Makushev!
Thank you very much for the feedback and an elaborate example of how you use it!
First of all, everybody should use whatever works for them the best but it’s always a good idea to explore other options 😉
Hi Lars Gyrup Brink Nielsen!
So the thing is that we import that lib module into our wrapper. That’s enough to lazy load it and display its own routes. (Check included project and demo, it works 😉)
We don’t want the parent app to use stuff from that lib, hence no exports, we only want to use it as a…
Hi Todd Palmer!
As always it depends! Let’s say you are building an library (oss / enteprise doesn’t matter) which provides some kind of specific functionality like data access or is a component framework.
In that case it makes sense to make schematics part of the library itself so that the library…
Thank you very much Todd Palmer!
Yes, it took quite a while and I am happy that you found it valuable!
ps: there is a new article in the pipeline which will be of same scope but about Angular services with
providedIn: ‘root’ syntax and how to configure them without the need for modules based on my…
Hi Kamil Maraz!
The thing is we DID call the schematics with
product code as a name and the helper functions then transformed it in the template to
classify string helper and also to
dasherize string helper so it’s not a typo!