[MGNLUI-3594] Consider introduction of SubAppLifecycle event Created: 18/Sep/15  Updated: 15/Apr/16  Resolved: 02/Nov/15

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.4.2
Fix Version/s: 5.3.12, 5.4.4

Type: Bug Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 2d
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLDAM-619 Temp files are not deleted after usin... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: Basel 18
Story Points: 5

 Description   

Similar to AppLifecycleEvent and dispatched by AppEventBus such an action could notify the interested parties (certain fields, dialogs, other sub-apps etc) of the initiation/focus/finalisation of a sub-app.

In particular, it would allow the components to clean up their resources once the sub-app is no longer in use.



 Comments   
Comment by Aleksandr Pchelintcev [ 18/Sep/15 ]

Provided we had SubAppLifecycleEvent - we could hook the DamUploadField to it and handle the deletion of tmp files once the sub-app dies.

Comment by Federico Grilli [ 04/Nov/15 ]

Won't be merged into 5.4.3 because it is not bringing a direct benefit without dependent tickets which are not planned for 5.4.3

Generated at Mon Feb 12 09:08:12 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.