aurelia/framework

Is there a way to destroy aurelia manually? force it to trigger detached() in all components

Open

#714 opened on Feb 12, 2017

View on GitHub
 (13 comments) (0 reactions) (0 assignees)TypeScript (11,747 stars) (671 forks)batch import
enhancementhelp wantedquestion

Description

I manually deleted the root tag "" by manipulating DOM directly, but found no detached() called in my custom-element.

I wonder if there is a way to destroy aurelia manually? for example, a api like aurelia.destroy() which will trigger detached() to be called in all components.

Contributor guide

Tech stack
javascripttypescript
Domain
frontendapi
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Aurelia lifecycleJavaScriptTypeScriptDOM manipulation
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the Aurelia framework source code in the `aurelia/framework` repository to understand the current lifecycle hooks, specifically the `detached()` method. Look for existing methods that tear down the application, such as `deactivate()` or `stop()`. Review the 13 comments in issue #714 for any proposed solutions or workarounds. Consider implementing a new public API method like `Aurelia.destroy()` that cleans up all components and triggers lifecycle hooks. Focus on the bootstrapping code in `src/` directory.