-
Improvement
-
Resolution: Done
-
Medium
-
None
-
None
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.
- relates to
-
YANGTOOLS-1127 Fix SchemaContextUtil.findDataSchemaNodeForRelativeXPath()
- Resolved