Open lllyfeng opened 1 year ago
Since module B did not have any changes, module B itself would not have any indications of an NBC change (there would not be a new version of module B created with a rev:non-backwards-compatible extension).
But if both module a and module b are part of a set of modules being compared (against other revisions of a and b) with a schema comparison tool, then the tool should point out the NBC change. IMO the tool should report: 1) the NBC change against each leaf that uses the typedef, and 2) the NBC change against the typedef itself
we can presume a grouping or a typedef is defined in one module, and this defintion is referenced by another module, if this definition has a nbc change, should all statements which reference this defiintion be nbc change?
For example: module a { revision-label "1.0.0"; typedef type1 { type uint32 { range 1..100; } } }
And module b { import a;
container b { leaf c { type a:type1; } } }
if module a change the type1's range to 1..50, the leaf c in module b should also have the nbc change? if yes, the module b have no any text change, how to express this change? if no, the scope of leaf c is reduced actually.