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.