Require QName instead of SchemaPath for TypeDefinition implementions
Description
relates to
Activity
Show:
Robert Varga January 28, 2021 at 4:24 PM
We ended up disabling the test for SchemaContextUtil – it will be re-enabled with https://lf-opendaylight.atlassian.net/browse/YANGTOOLS-1127#icft=YANGTOOLS-1127.
Done
Details
Details
Assignee
Robert Varga
Robert VargaReporter
Robert Varga
Robert VargaComponents
Fix versions
Priority
Medium
Created January 28, 2021 at 11:39 AM
Updated January 28, 2021 at 4:24 PM
Resolved January 28, 2021 at 4:24 PM
TypeDefinition has no semantics dependent on SchemaPath, just QName – ever since https://lf-opendaylight.atlassian.net/browse/YANGTOOLS-1098#icft=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.