General Session
Run Code When Leaving Your Angular Application
We have all seen and likely used the ngOnDestroy lifecycle hook. But did you know it doesn’t fire when the browser tab is refreshed or closed or the URL is changed to a new page? What do you do if you need to do some cleanup when the entire Angular app is destroyed? That’s where this talk will come in handy.
General Session
Run Code When Leaving Your Angular Application
We have all seen and likely used the ngOnDestroy lifecycle hook. But did you know it doesn’t fire when the browser tab is refreshed or closed or the URL is changed to a new page? What do you do if you need to do some cleanup when the entire Angular app is destroyed? That’s where this talk will come in handy.