JSON namespace-qualified names not supported about yang HOT 4 CLOSED

from yang.

Hi, thx for the reply.

In a nutshell, I have an identityref leaf using a derived type defined in an imported yang module. When processing the leaf, this code:
func toIdentRef(base *meta.Identity, v interface{}) (val.IdentRef, error) {
var empty val.IdentRef
x := fmt.Sprintf("%v", v)
ref, found := base.Derived()[x]
//...
}

compares namespace-qualified name receive in the JSON with the derived type name without the namespace. In other words it compares A:B with B. Which fails. If I remove the namespace from the JSON body, it works fine.

I can provide a small example if needed.

Thx

from yang.

Hi,

A quick and dirty example that will panic at startup:

main.go.txt
Module-test.yang.txt
Module-types.yang.txt

If you remove the namespace ("type":"derived-type") it works... But when getting back the "type" leaf you get this result:
GET http://localhost:8090/restconf/data/Module-test
{
"Module-test:type": "derived-type"
}

Here the namespace is applied to the key and not the value which is incorrect as far as I know. type doesn't require a namspace since it's already in Module-test namespace and the derived type needs to be prefixed.

As a reference, section 6.8 of RFC7951.

Thx

from yang.

I was able to duplicate this and spec reference confirms your assertion. I should have fix and unit test in next couple days, thanks for reporting!

from yang.