Details
-
Story
-
Status: Confirmed
-
Medium
-
Resolution: Unresolved
-
None
-
None
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.
Attachments
Issue Links
- relates to
-
YANGTOOLS-1290 Deprecate SchemaAware NormalizedNode builders
-
- Resolved
-
1.
|
Do not use DataSchemaNode in Anydata normalization |
|
Resolved | Robert Varga |
2.
|
Promote yang.data.impl.SchemaTracker |
|
Resolved | Robert Varga |
3.
|
Remove SchemaUtils methods |
|
Resolved | Robert Varga |
4.
|
Deprecate JSONNormalizedNodeStreamWriter.create*Writer() with SchemaPath |
|
Resolved | Robert Varga |
5.
|
Deprecate XMLStreamNormalizedNodeStreamWriter.create() with SchemaPath |
|
Resolved | Robert Varga |
6.
|
Remove SchemaAware NormalizedNode builders |
|
Resolved | Robert Varga |
7.
|
Add DataSchemaContext.SimpleValue.type() |
|
Resolved | Robert Varga |
8.
|
Do not use yang.model.api.Module in AbstractModuleStringInstanceIdentifierCodec |
|
Resolved | Robert Varga |
9.
|
Create a yang-data-api equivalent of TypeDefinition |
|
Confirmed | Unassigned |
10.
|
Extract yang.data.impl.codec to yang-data-util |
|
Confirmed | Unassigned |
11.
|
Migrate InMemoryDataTree to use EffectiveStatements |
|
Confirmed | Unassigned |
12.
|
Do not use SchemaContext.findModule(s) |
|
Resolved | Robert Varga |