Do not use SchemaNode in yang-data
(YANGTOOLS-1244)
|
|
| Status: | Resolved |
| Project: | yangtools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0 |
| Type: | Sub-task | 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: |
|
||||||||
| Description |
|
NormalizedAnydata and NormalizableAnydata rely on DataSchemaNode to provide enough context to decode the data. This is made with the implicit assumption that DataSchemaNode.getPath() provides the context needed to perform things like leafref resolution. We have a better replacement in EffectiveStatementInference, which combines an EffectiveModelContext with an ordered list of EffectiveStatements – providing a simple-to-use alternative. |
[YANGTOOLS-1245]