v0.12.2

• [ypathgen]: Use correct schema entry for determining package name.

v0.12.1

• [ypathgen] Allow generation of multiple path struct packages instead of one single package (@DanG100).
• [ypathgen] add GoPathPackageName to NodeData (@DanG100).
• [ypathgen] ResolvePath should return a non-nil PathElem message.
• Don't import ywrapper and yext proto files if not used.
• Update proto generation commands to the most recent and update README.

v0.12.0

• Fix bug when JSON Marshalling augments when using compressed schemas where the augmented node is within config/state.
• Improve testing coverage a little and minor refactoring.
• Generate enumerated types in ΛEnumTypes in schema order to ensure that when unmarshalling string -> union type, that the enumerated types will be looped through in the right order (see #430).
• Reject relative paths for leafref's path statement.
• Update goyang dep to v0.2.9, which includes fix for openconfig/goyang#131.
• Add go:generate directives for (u)exampleoc/... generated code.

v0.11.3

• Add IgnoreAdditions option for ygot.Diff for checking whether A is a subset of B (@dan-lepage).
• Update leaf getter comment to say default value will be returned when unset.
• Add HasDefault field to NodeDataMap returned by ypathgen.

v0.11.2

• [Go]: Resolve conflict when a multi-keyed list contains a container named "key".

v0.11.1

• Add Fakeroot to NodeDataMap return value for ypathgen's GeneratePathCode.

v0.11.0

• Add key to shadow-path annotation.
• Change reverseShadowPath -> preferShadowPath for [Getxxx|Set]Node functions (backwards incompatible).

v0.10.16

• Add support for a new marshalling option that allows the module prefix applied to JSON output serialised according to RFC7951 to be removed.

This specifically handles a case whereby YANG augmentations are used to handle backwards compatibility. For example, in the schema "openconfig-foo" if leaf bar was removed, and consumers of the generated GoStructs are using this field - a compatibility approach is to create a module which augments openconfig-foo to add leaf bar back in - perhaps in some module acme-corp-compatibility. In this case, the JSON produced by Marshal7951 with AppendModuleName = true would use this prefix acme-corp-compatibility, this change allows the user to specifically force it to be rewritten to openconfig-foo again to maintain compatibility with a particular downstream consumer.

v0.10.15

• Don't initialize leaf values when unmarshalling valid shadow paths.
  • Also remove support for any shadow paths of depth > 1 to reduce code complexity. This is sufficient for the OpenConfig use case. Shadow paths is only relevant for compressed schemas, which is a peculiarity to OpenConfig.

v0.10.14

Add support for mapping compressed schemas into protomap.