[YANGTOOLS-1244] Do not use SchemaNode in yang-data Created: 14/Feb/21 Updated: 05/Jan/24 |
|
| Status: | Confirmed |
| Project: | yangtools |
| Component/s: | codecs, data-impl |
| Affects Version/s: | None |
| Fix Version/s: | 14.0.0 |
| Type: | Story | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Unassigned |
| Resolution: | Unresolved | 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 |
| Description |
|
We now have fully-featured replacement for SchemaNode in EffectiveStatement, with enough tooling to cover all yang-data use cases as well as bridging methods for users to cross, for example, from ContainerSchemaNode to ContainerEffectiveStatement. Migrate all users of SchemaNode within *-data-* artifacts to use EffectiveStatement and its specializations. |