Abtract component and UntilDestroy decorator
See original GitHub issueI have the same issue as Issue 50
I use Angular 9 and the error is
Cannot read property 'onDestroy' of undefined
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:13 (2 by maintainers)
Top Results From Across the Web
angular - Ensure super.onDestroy() in derived component
The simplest solution is to define a return type of ngOnDestroy that the child needs to return as well. class REQUIRED_SUPER {} //important ......
Read more >@ngneat/until-destroy - npm
RxJS operator that unsubscribes when Angular component is destroyed. Latest version: 9.2.2, last published: 4 months ago.
Read more >Unsubscribe | npm.io
@writetome51/unsubscribe-on-destroy-component. Abstract Angular component that unsubscribes from subscriptions during ngOnDestroy() ... ngx-until-destroy.
Read more >Complete List of Angular Utilities Libraries
It helps writing data-agnostic and design-agnostic components so it will help your ... to be an abstract layer to easily generate dynamic forms...
Read more >Harnessing the power of Mixins in Angular - HackerNoon
Of course, this is great, but for most components (like, 90%) the ... Using the untilDestroyed() function and its pipeable features, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @arturovt, I know it is an open source project and you have your own priorities but do you have any idea when someone would be able to take a look at this issue (days, weeks, months)? The way things are right now there is no parity between @ng-neat/until destroy and ngx-take-unti-destroy functionality and you really should mention this in the migration docs so that others are aware of possible issues.
Closing as fixed. Feel free to open an issue if the problem persists.