[MGNLUI-4999] Revisit UI context components clean-up/destruction mechanisms Created: 05/Feb/19 Updated: 12/Sep/19 Resolved: 11/Sep/19 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Aleksandr Pchelintcev | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 7h 25m | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Epic Link: | UI framework: basic features |
| Sprint: | UI Framework 2, UI Framework 6 |
| Story Points: | 8 |
| Description |
|
We've introduced view destruction functionality, which allows to unregister it and clean-up the bean storages of it and its child views. However, the accompanying objects, like presenters, observers etc might also need destruction which at this point is done via type checking (i.e. instanceof Destructible and manual call of destroy method. Problem is that most of such manually cleaned-up objects are actually created by the view and could be managed/tracked along-side of the view and could be destroyed along with it. goals:
|