Re: [netmod] RPC input parameter definition order (uses augment)

[Kent Watsen <[e-mail]>]

Hi Jernej,

> RFC7950, 7.14.4. says:
> 
>    Input parameters are encoded as child XML elements to the rpc node's
>    XML element, in the same order as they are defined within the "input"
>    statement.
> 
> For the following model:
> 
> module b {
>   namespace "b:uri";
>   prefix b;
> 
>   grouping params {
>     container params {
>       leaf x {
>         type string;
>       }
>     }
>   }
> 
>   rpc foo {
>     input {
>       uses params {
>         augment params {
>           leaf y {
>             type string;
>           }
>         }
>       }
>     }
>   }
> }
> 
> If both "leaf" data nodes are instantiated (XML encoding) as part of <rpc> for "foo", does <x> come before or after <y> (in document order)?

Augmented-in nodes come after other nodes. 

I’ve always wished there were a way to specify where they’re placed, for readability, but it’s too inconsequential to raise as an issue here. 

> Jernej

Kent