You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@ockan@Injectable is used to define the lifetime scope of the provider object.
If you don't use @Injectable, and you register the service on the AppFactory or Module the application will assume the provider as a singleton scope.
Also, providers in AppFactory or `Module' are registered in the Ellar DI container making them available for injection.
But @ockan, if you feel there are other ways this could be made easy, please share, I would love to hear your suggestion.
Now,to realize the provider,3 steps needed:
1\declare the injectable service:

2\give it as a argument of AppFactory:

3\use really the provider:

that is complex.why need to use the decorator '@Injectable'? why need to register provider to AppFactory?it is confused.
The text was updated successfully, but these errors were encountered: