Closed jdillard closed 5 years ago
Augment statements are supported. Thus what you observe is most likely a bug. Are you able to share yang you are using while observing this NPE? If not are you able to provide artificial example leading to that error?
I am working on simplifying the YANG as much as possible so there is less to troubleshoot. It seems that error might be caused by augmenting an empty container, such as:
container turing-machine {
description
"State data and configuration of a Turing Machine.";
}
augment "/tm:turing-machine" {
description
"State data for the second tape.";
leaf head-position-2 {
type tm:cell-index;
config "false";
description
"Head position of the second tape.";
}
container tape-2 {
config "false";
description
"Contents of the second tape.";
uses tm:tape-cells;
}
}
I have been using these two yang files as a control, since they seem to work fine with yang2swagger. I just stripped out all the leafs/containers and the augment statements related to them for the above code sample.
When I add a leaf to the empty container in my yang I get a different error, so I am still troubleshooting there, but maybe that helps a little.
Looks like it was some (bad) changes we made to support namespaces, but using the -use-namespaces
flag @UltimateDogg added worked fine. Sorry for taking up your time!
I have some yang files that use the augment statement and yang2swagger seems to be overriding models, because I get a bunch of the following:
But then I get the following error due to
m.getProperties()
beingnull
:The augmented yang files are processed fine by pyang, so the syntax should be correct. Is it possible the augment statement isn't fully supported or am I doing something wrong?