[YANGTOOLS-1098] Remove references to SchemaNode.getPath() in TypeDefinitions Created: 17/Apr/20  Updated: 10/Apr/22  Resolved: 01/Oct/20

Status: Resolved
Project: yangtools
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0

Type: Task Priority: High
Reporter: Robert Varga Assignee: Robert Varga
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MDSAL-569 Eliminate use of SchemaPath from DOM ... Resolved
relates to MDSAL-581 Expose action path lookup from Bindin... Resolved
Epic Link: Get rid of SchemaNode.getPath()

 Description   

TypeDefinition hashCode/equality is defined in terms of utility methods. These currently rely on the definition's SchemaPath. Redefine these methods to refer only to the type's QName instead.

 Comments   
Comment by Robert Varga [ 17/Apr/20 ]

Non-exhaustive list of methods:

  • TypeDefinitions.basicHashCode()
  • TypeDefinitions.hashCode()
  • TypeDefinitions.equals()
  • BinaryTypeDefinition.hashCode()
  • BinaryTypeDefinition.equals()
Comment by Robert Varga [ 03/Jul/20 ]

The leitmotiv here is that a TypeDefinition is not a SchemaNode, but rather a DocumentedNode.WithStatus which also happens to have a QName. I think the QName part should be isolated into a separate interface during this.

Generated at Wed Feb 07 20:55:11 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.