[YANGTOOLS-1270] Instantiate EffectiveRevisionDate statements on linkage Created: 13/Apr/21 Updated: 05/Jan/24 |
|
| Status: | Confirmed |
| Project: | yangtools |
| Component/s: | parser |
| Affects Version/s: | None |
| Fix Version/s: | 14.0.0 |
| Type: | Improvement | Priority: | Low |
| Reporter: | Robert Varga | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | pt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Epic Link: | Accurate EffectiveStatements | ||||||||
| Description |
|
Our parser does not reflect the result of inter-module linkage (via import) into the effective model. This means users trying to cross-reference EffectiveModuleStatements need to perform their own re-linkage because they have no way of finding out how a particular import was resolved. Improve parser so that for a revisionless import: module foo {
import bar {
prefix bar;
}
}
we introduce an undeclared EffectiveRevisionDate statement which reflects the revision of the imported module. i.e. when linked with: module bar {
revision 2010-11-12;
}
the effective model of foo looks as if it was declared: module foo {
import bar {
prefix bar;
revision-date 2010-11-12;
}
}
|