On 15/09/2017 11:21, Ladislav Lhotka wrote:
Andy Bierman píše v Čt 14. 09. 2017 v 08:43 -0700:
Hi,
Actually I liked the early pyang output that was concise and easy to remember.
The current format gets very cluttered and there are too many little symbols
to remember them all.
I agree.
I definitely think that "x" is a bit confusing since it both means "RPC"
and also "status deprecated" depending on where it is.
Thanks,
Rob
Lada
Andy
On Thu, Sep 14, 2017 at 8:33 AM, Joe Clarke <[email protected]> wrote:
I've been hacking on pyang, and I changed tree.py to add the enum values
for enumeration types and identiyref bases for identityref types. Here
is an example:
module: yang-catalog
+--rw catalog
+--rw modules
| +--rw module* [name revision organization]
| +--rw name yang:yang-identifier
| +--rw revision union
| +--rw organization string
| +--rw ietf
| | +--rw ietf-wg? string
| +--rw namespace inet:uri
| +--rw schema? inet:uri
| +--rw generated-from? enumeration [mib, code,
not-applicable, native]
| +--rw maturity-level? enumeration [ratified,
adopted, initial, not-applicable]
...
+--rw protocols
| +--rw protocol* [name]
| +--rw name
identityref -> protocol
...
My questions are:
1. Is this useful?
2. If so, can this be added to pyang (happy to submit a PR) and
draft-ietf-netmod-yang-tree-diagrams?
3. What changes to the output format would you recommend?
Thanks.
Joe
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
