Resolve yang-parser-spi naming
Description
Activity
Show:
Robert Varga
changed the PriorityFebruary 6, 2025 at 2:13 PMHigh (migrated)
Robert Varga
updated the Fix versionsJuly 4, 2024 at 11:19 AMNone
15.0.0
Robert Varga
updated the Fix versionsJuly 4, 2024 at 11:19 AM14.0.0
None
Robert Varga
updated the Fix versionsJanuary 5, 2024 at 3:12 PMNone
13.0.0
Robert Varga
updated the Fix versionsJanuary 5, 2024 at 3:12 PM12.0.0
None
Robert Varga
updated the Fix versionsMay 29, 2023 at 12:19 PM11.0.0
None
Robert Varga
updated the Fix versionsMay 29, 2023 at 12:19 PMNone
12.0.0
Robert Varga
updated the Fix versionsOctober 4, 2022 at 12:31 PM10.0.0
None
Robert Varga
updated the Fix versionsOctober 4, 2022 at 12:31 PMNone
11.0.0
Robert Varga
updated the Fix versionsJune 7, 2022 at 11:21 AMNone
10.0.0
Robert Varga
updated the Fix versionsJune 7, 2022 at 11:21 AM9.0.0
None
Robert Varga
updated the Fix versionsFebruary 9, 2022 at 7:30 PMNone
9.0.0
Robert Varga
updated the Fix versionsFebruary 9, 2022 at 7:30 PM8.0.0
None
Robert Varga
updated the Fix versionsApril 19, 2021 at 1:48 PMNone
8.0.0
Robert Varga
updated the Fix versionsApril 19, 2021 at 1:48 PM7.0.0
None
Robert Varga
changed the StatusNovember 1, 2020 at 6:07 PMOpen
Confirmed
Robert Varga
created the IssueOctober 21, 2020 at 4:39 PMDetails
Details
Assignee
Unassigned
UnassignedReporter
Robert Varga
Robert VargaComponents
Fix versions
Priority
Created October 21, 2020 at 4:39 PM
Updated February 6, 2025 at 2:13 PM
yang-parser-spi currently holds content which is quite ungroomed. It has all sorts of things:
org.opendaylight.yangtools.yang.parser.spi.meta.AbstractDeclaredStatement. This actually is yang-model-spi stuff and we have a replacement in yang-parser-rfc7950
org.opendaylight.yangtools.yang.parser.spi.meta.CopyHistory. This is yang-parser-rfc7950-(api|spi) stuff, as it relates to the implementation.
org.opendaylight.yangtools.yang.parser.spi.source.BelongsToModuleContext et al. are clearly YANG-specific and are clearly yang-parser-rfc7950-spi (i.e. exposed to plugins)
parser.spi.validation – that is completely unclear, but definitely not visible to the causal user
Clean all this up, shifting it to new componenets. yang-parser-spi will probably end up being very thin with things relating to yang-parser-api implementation!