[YANGTOOLS-951] Fix ListEntry-rooted InMemoryDataTree integration Created: 05/Feb/19 Updated: 05/Feb/19 Resolved: 05/Feb/19 |
|
| Status: | Resolved |
| Project: | yangtools |
| Component/s: | data-impl |
| Affects Version/s: | None |
| Fix Version/s: | 3.0.0, 2.0.17, 2.1.9 |
| Type: | Improvement | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Epic Link: | unlabeled-YANGTOOLS-940 | ||||||||
| Description |
|
Current implementation of MapModificationStrategy allows both map entries and the entries' children to be accessed. This is a badly-integrated approach to making InMemoryDataTree work when rooted in a MapEntryNode. Rework the integration so that proper ListEntryModificationStrategy is resolved as the root strategy, thus eliminating the need for this workaround. |