On 9/14/17 11:43, Andy Bierman 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 just went with text for these changes. Yes, it adds more verbiage to the output, but it doesn't add any cryptic symbols; plus I think it makes it easier to comprehend the types. Joe > > > Andy > > > On Thu, Sep 14, 2017 at 8:33 AM, Joe Clarke <jcla...@cisco.com > <mailto:jcla...@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 <mailto:netmod@ietf.org> > https://www.ietf.org/mailman/listinfo/netmod > <https://www.ietf.org/mailman/listinfo/netmod> > > _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
