[YANGTOOLS-1118] Remove DocumentedNode and its subclasses (SchemaNode, etc.) Created: 03/Jul/20  Updated: 03/Jul/20

Status: Confirmed
Project: yangtools
Component/s: parser
Affects Version/s: None
Fix Version/s: None

Type: Epic 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

Epic Name: Remove DocumentedNode

 Description   

DocumentedNode view of the world is an antiquated design, which is superseded by ModelStatement and its two specializations, DeclaredStatement and EffectiveStatement.

When DocumentedNode aimed to have an object model easy to use in Binding Spec, it has a number of quirks which make it hard (and inefficient) to use in other settings.

While EffectiveStatements are not as feature-rich yet, they are very close to providing everything needed for users to use them instead of SchemaNode.

Evolve both API contracts so that switching users becomes possible without wholesale removals, enriching EffectiveStatements with metadata they do not yet hold. The end goal here is removal of DocumentedNode and all interfaces which directly reference it.


Generated at Wed Feb 07 20:55:14 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.