https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/YANGTOOLS-1216 yangtools <p>TypeDefinition has no semantics dependent on SchemaPath, just QName – ever since <a href="https://jira.opendaylight.org/browse/YANGTOOLS-1098" title="Remove references to SchemaNode.getPath() in TypeDefinitions" class="issue-link" data-issue-key="YANGTOOLS-1098"><del>YANGTOOLS-1098</del></a>.</p> <p>Since <a href="https://git.opendaylight.org/gerrit/q/I3490d6d706113ea14ee3f4181a7ba827380c8181" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/q/I3490d6d706113ea14ee3f4181a7ba827380c8181</a> the default SchemaPath contract throws an UOE.</p> <p>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.</p> YANGTOOLS-1216

Require QName instead of SchemaPath for TypeDefinition implementions

Improvement Medium Resolved Done Robert Varga Robert Varga Thu, 28 Jan 2021 11:39:08 +0000 Thu, 28 Jan 2021 16:24:11 +0000 Thu, 28 Jan 2021 16:24:11 +0000 7.0.0 model-util 0 1 <p>We ended up disabling the test for SchemaContextUtil – it will be re-enabled with <a href="https://jira.opendaylight.org/browse/YANGTOOLS-1127" title="Fix SchemaContextUtil.findDataSchemaNodeForRelativeXPath()" class="issue-link" data-issue-key="YANGTOOLS-1127"><del>YANGTOOLS-1127</del></a>.</p> Relates YANGTOOLS-1127 Development Epic Link YANGTOOLS-1066 Rank 0|i03wwv: