[YANGTOOLS-1153] Audit users of NamespaceBehaviour.global() Created: 28/Oct/20 Updated: 04/Oct/22 Resolved: 04/Oct/22 |
|
| Status: | Resolved |
| Project: | yangtools |
| Component/s: | parser |
| Affects Version/s: | None |
| Fix Version/s: | 10.0.0 |
| Type: | Improvement | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | pt | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Sub-Tasks: |
|
|||||||||||||||
| Epic Link: | Parser Performance |
| Description |
|
There are a few global namespaces, identified by invoking NamespaceBehaviour.global() to derive their behaviour. Search for all users of such namespaces and look how they access them. In the end we want all such users to go through a a direct lookup of root. From API safety perspective, I think the best option would be to mark global namespaces with GlobalNamespace and require NamespaceBehavior.global(Class <? extends GlobalNamespace). This needs some investigation, perhaps we should expose root to all places where we send StmtContext.
|
| Comments |
| Comment by Robert Varga [ 04/Oct/22 ] |
|
All callers are accounted for and the behaviour/namespace link is further examined in |