[YANGTOOLS-1111] Cleanup CompositeNodeDataWithSchema instantiation, logic and users Created: 09/Jun/20 Updated: 23/Aug/20 |
|
| Status: | Confirmed |
| Project: | yangtools |
| Component/s: | data-util |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
CompositeNodeDataWithSchema is an intermediate representation geared towards keeping schema and data parsing state when we do not have proper encapsulation in encoding (like XML). The API towards codecs and between parent/child nodes seems to be very fragile, especially when we consider choice/case instantiation and dealing with duplicate nodes. Revisit the implementation and its callers to ensure the API surface is crisp and provides adequate performance. |