Uploaded image for project: 'yangtools'
  1. yangtools
  2. YANGTOOLS-1118

Remove DocumentedNode and its subclasses (SchemaNode, etc.)

    XMLWordPrintable

Details

    • Epic
    • Status: Confirmed
    • Medium
    • Resolution: Unresolved
    • None
    • None
    • parser
    • None
    • 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.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            Unassigned Unassigned
            rovarga Robert Varga
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: