aurelia/framework

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

Open

#714 建立於 2017年2月12日

在 GitHub 查看
 (13 留言) (0 反應) (0 負責人)TypeScript (11,747 star) (671 fork)batch import
enhancementhelp wantedquestion

描述

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.

貢獻者指南

技術棧
javascripttypescript
領域
frontendapi
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Aurelia lifecycleJavaScriptTypeScriptDOM manipulation
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
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.