- Implemented a service. App-wide one - gets provided in
AppModule
. Eagerly i.e. at app start, before components get loaded. - Inject service in
TimeWidgetComponent
. Service is provided inAppModule
- Destroy component
- Expect service to get destroyed?
- It is not destroyed.
Alternative
- Inject service in
FeedComponent
provided inFeedComponent
- Destroy component
- Expect service to get destroyed?
- It does get destroyed?
My take on that:
FeedComponent
provides the service and component does get destroyed and in turn it destroys its 'destructable' providersAppModule
provides the service but never gets destroyed until user navigates away from our site at which point the Garbage collector is responsible for eventually cleaning that memory
This project was generated with Angular CLI version 1.6.8.
Run ng serve
for a dev server. Navigate to http://localhost:4200/
. The app will automatically reload if you change any of the source files.
Run ng generate component component-name
to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module
.
Run ng build
to build the project. The build artifacts will be stored in the dist/
directory. Use the -prod
flag for a production build.
Run ng test
to execute the unit tests via Karma.
Run ng e2e
to execute the end-to-end tests via Protractor.
To get more help on the Angular CLI use ng help
or go check out the Angular CLI README.