[MAGNOLIA-7641] Consider bubbling modification status to parent nodes [at least for the assets] Created: 01/Oct/19  Updated: 08/Oct/19  Resolved: 07/Oct/19

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2

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

Issue Links:
causality
is causing MGNLDAM-804 AssetAndNodeBaseCachingStrategy consi... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Sprint: UI Framework 7

 Description   

Whenever we change something under the page node - it is automatically marked as modified as well.
Assets store content in separate node and -> should logically follow the same logic, but they don't, which leads to issues like the linked one.

We need to make sure that the pattern we have for pages (and also for users) spreads on the assets. All that has to be done is that the node wrapper responsible for the last mod update would know how far to propagate it up the parent tree (MgnlPropertySettingContentDecorator that is). In case of pages - it is always mgnl:page, in case of users - mgnl:user.., in case of assets - should be mgnl:asset. The former two are hardcoded, the last belongs to a different module (dam), but we can at least custom string mapping.

In the best case scenario the strategy should be injectable, just like the TODO in MgnlPropertySettingContentDecorator.


Generated at Mon Feb 12 04:25:33 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.