hi guys,
I've created a PR with @jjenzz suggestion.
Also added a test which checks that when ngOnDestroy occurs on a component, the subject of other instances is not completed.
The test will fail with the current code and will pass with the fix
@NetanelBasal I've updated a bit the npm scripts. hopefully they make sense.
feel free to suggest any updates if you prefer anything to be / look different
Fixes https://github.com/NetanelBasal/angular2-take-until-destroy/issues/5
@NetanelBasal @jjenzz
hi guys, I've created a PR with @jjenzz suggestion.
Also added a test which checks that when
ngOnDestroy
occurs on a component, the subject of other instances is not completed.The test will fail with the current code and will pass with the fix
@NetanelBasal I've updated a bit the npm scripts. hopefully they make sense. feel free to suggest any updates if you prefer anything to be / look different