[YANGTOOLS-1070] Allow YANG parser to not create SchemaPaths in SchemaNodes Created: 15/Jan/20 Updated: 29/Aug/21 Resolved: 29/Aug/21 |
|
| Status: | Resolved |
| Project: | yangtools |
| Component/s: | parser |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | Get rid of SchemaNode.getPath() |
| Description |
|
Add an option (environment-default) where YANG parser will not expose SchemaNode.getPath(), but rather will throw UnsupportedOperationException when the method is called. Class layout should not suffer much – the field currently used for SchemaPath can be made polymorphic (i.e. declared as Object) and dispatch getQName() and getPath() based on either run-time type of the object or based on a runtime constant. |
| Comments |
| Comment by Robert Varga [ 29/Aug/21 ] |
|
The fallout from |