[YANGTOOLS-853] Fix EffectiveStatement namespace implementation Created: 26/Feb/18 Updated: 13/Jun/18 |
|
| Status: | Confirmed |
| Project: | yangtools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Low |
| Reporter: | Robert Varga | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Description |
|
EffectiveStatement interface has provisions to lookup entities based on IdentifierNamespace. This capability is unfortunately unimplemented, which leads to users having to use SchemaNodes and weird hacks to get to information which should be exposed as namespaces.
|
| Comments |
| Comment by Robert Varga [ 13/Jun/18 ] |
|
The only unimplemented namespaces are groupings and typedefs. Both of these are hierarchical namespaces scoped to descendants, which makes them not very useful when walking the tree. We can revisit this when needed. |
| Comment by Robert Varga [ 13/Jun/18 ] |
|
Data tree view has the side-effect of detecting duplicate nodes. |