与在应用程序组件中使用服务作为提供者相比，providedIn: 'Root' 之间有什么区别？

Question

If I set a service as a provider at the app module (root module) or at the decorator @Injectable use providedIn: 'root', I assume that I will achieve the same behavior in both cases. That means all my application will "see" the same singleton class provided by the root module.

But If I don't set any module at the @Injectable decorator on the service and use that class as a provider at the app component module, I am not able to see that same service within components that are not 'created' by my template. For example, I can't use that service inside a MatDialog, that is created and opened using TS and not my template.

That being said, what is the technical difference between those approaches?

Answer 1

They introduced providedIn: 'root' to make it easier to manage services. Most services are stateless singleton services. providedIn: 'root' is essentially the same as just adding the service at the app.module level in the providers array. However, it was easy to forget to add this entry and an unnecessary extra step.

Obviously, if you don't want a singleton service and would rather provide stateful services at various levels then the providers array is still available. It would be confusing to scrap it at the app.module level just because providedIn: root covers this.