Wen Bo Li
Wen Bo Li
Have only one place (ygnmi) where path structs can be generated, so that we don't have two different ways of doing so.
Currently, `ParsedDirectory` is keyed on the "total" schema path of the node. So this includes choice/cases statements for a YANG schema that uses them. This was noted as questionable by...
Currently, the generated proto code uses the default value as the first/default enum value for all "leaf" (not leaf-list) enumerated values. Because in proto the enum definition alone can specify...
With the recent rename of `Validate` to `ΛValidate`, the `ygot.ValidatedGoStruct` interface has become less usable, not to mention this being a breaking change in order to allow nodes named `validate`...
```go // PrependModuleNameNonRootTopLevel specifies that the top-level field // names of a non-root ValidatedGoStruct being marshalled should always // have their belonging-module names prepended in the JSON output, // instead...
Go 1.18 has been released and some parts of ygot will benefit from it, esp. libraries that operate on GoStructs or PathStructs. https://tip.golang.org/doc/devel/release#go1.18
Returning this message for UNSET seems rather excessive, as reflected by a user: `fmt.Sprintf("out-of-range %s enum value: %v", enumTypeName, val)` Since all UNSET values are currently 0, we can just...
#292 would fix the case for straight-up empty-type leaves. But it doesn't address unmarshalling a union leaf that contains an empty type. 1. Is this unlikely to occur in practice?...
Any `PathStruct` should be able to represent the fully qualified path. Therefore, generation should get the origin information from the input YANG model and store that information in it so...
[]byte is unhashable, which means it currently causes the code to not compile when it's the key of a list. However, the new union API had wanted to support this...