Re: [netmod] Proposal to enhance the YANG tree output

Hi Joe,
> On 9/14/17 13:50, Martin Bjorklund wrote:
>> Andy Bierman <andy@yumaworks.com> wrote:
>>> 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 with Andy.  I also did some experiments with printing
>> enumerations, and they work ok for small enums.  But once you have
>> more than a handful they do tend to clutter the output.  Even worse so
>> for trees that go into RFCs (where lines need to be < 70 characters).
> What about protecting this with an optional parameter?  I certainly
> appreciate the output could be large, but I think it does have its uses
> sometimes.
I would agree it has its uses sometimes.
And it helps the broader community with understanding YANG, this is good.
Now, if you are already a YANG expert, I guess you don't use the tree 
output much.

Regards, Benoit (as a contributor)
>
> Joe
>
>> Lada is sometimes using a format with even less information, where he
>> has removed all type information, focusing more on the structure.
>>
>>
>> /martin
>>
>>
>>
>>>
>>> Andy
>>>
>>>
>>> On Thu, Sep 14, 2017 at 8:33 AM, Joe Clarke <jclarke@cisco.com> 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
>>>> netmod@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/netmod
>>>>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
> .
>