[MGNLUI-4578] Make JCR-bound Tree/List views resilient to the underlying workspace changes Created: 17/Aug/18 Updated: 01/Apr/19 Resolved: 01/Apr/19 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 6.0 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Aleksandr Pchelintcev | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
|||||||||||||||||||||||||
| Sub-Tasks: |
|
|||||||||||||||||||||||||
| Template: |
|
|||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
|||||||||||||||||||||||||
| Task DoR: |
Empty
|
|||||||||||||||||||||||||
| Description |
|
Apparently Grid/TreeGrid components do not behave that well when the underlying datasource changes especially with regard to the move/remove item operations. In particular, regarding JCR domain with the fragile session-dependent nodes, Grid/TreeGrid might blow up with exceptions:
Related logic is located in e.g. DataCommunicator.ActiveDataHandler and DataKeyMapper - those are responsible for keeping mapping information between client-side ids vs the domain items (nodes in this case). Clearing out stale/no longer existing nodes is tedious - for that we have to override DataCommunicator and HierarchyMapper (for the flat Grid). |