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

Require QName instead of SchemaPath for TypeDefinition implementions

    XMLWordPrintable

Details

    • Improvement
    • Status: Resolved
    • Medium
    • Resolution: Done
    • None
    • 7.0.0
    • model-util
    • None

    Description

      TypeDefinition has no semantics dependent on SchemaPath, just QName – ever since YANGTOOLS-1098.

      Since https://git.opendaylight.org/gerrit/q/I3490d6d706113ea14ee3f4181a7ba827380c8181 the default SchemaPath contract throws an UOE.

      This makes TypeDefinition.getPath() a pure implementation detail. This ends up being costly in terms of memory overhead (SchemaPath vs QName) as well as accidental mis-features, such as seemingly guaranteeing type definition uniqueness.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. YANGTOOLS-1127 Fix SchemaContextUtil.findDataSchemaNodeForRelativeXPath()

          • High - Serious problem that could block progress.
          • Resolved
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: