Metadata
- Source
- FLUID-4890
- Type
- Improvement
- Priority
- Blocker
- Status
- Closed
- Resolution
- Fixed
- Assignee
- Antranig Basman
- Reporter
- Antranig Basman
- Created
2013-01-16T14:57:30.162-0500 - Updated
2019-08-01T09:30:58.612-0400 - Versions
- N/A
- Fixed Versions
-
- 1.5
- Component
-
- Framework
Description
During our authoring call about FLUID-4884, Yura suggested that an important and confusing source of errors was caused by listeners registered with "zombie components" that have already been destroyed. After a component's onDestroy has fired, there should be a hard and immediate error triggered by any listener notifying it, in order to make debugging this kind of issue as clear and direct as possible
Comments
-
Justin Obara commented
2013-12-09T08:35:05.797-0500 More conversation on the pull request
https://github.com/fluid-project/infusion/pull/443 -
Michelle D'Souza commented
2014-05-13T13:56:30.096-0400 Merged into project repo at f5403d5027923475e0c4314005f6723d2e732759
-
Antranig Basman commented
2019-08-01T09:30:58.612-0400 Note that we now by policy implement a different behaviour - any component action triggered after destruction, e.g. an invoker or listener call, is now a no-op