Hi Kent, it's not exactly what you are asking for but FWIW Yangson has a method DataModel.schema_digest [1] that returns a “schema digest” - a JS object that contains all information that is necessary for such a client-side web app - data tree structure, types, restrictions and more. I used it successfully for writing a RESTCONF client app in AngularJS.
I discussed this once with Martin Björklund and I think he mentioned that tail-f used something similar. Perhaps this could be an idea for standardizing - apart from web apps there are other restricted environments not well suited for dealing with all the complexity and modularity of YANG data models. Happy New Year to everyone, Lada [1] https://yangson.labs.nic.cz/datamodel.html#yangson.datamodel.DataModel.schema_digest Kent Watsen <kent+i...@watsen.net> writes: > In the “here’s something different” category… > > I’m interested in creating an SPA (single page application) on top of a > RESTCONF server. > > Popular SPA frameworks include AngularJS, Ember.js, ExtJS, Knockout.js, > Meteor.js, React, Vue.js, and Svelte. TypeScript is a used by these > frameworks to “type” the data (since JavaScript is natively untyped). In > this case, the data is defined in YANG, so it seems that tooling could create > a hierarchy of TypeScript types. But searching didn’t find any such thing... > > I’m sure folks are creating SPAs on top of RESTCONF. Can anyone share a > toolchain that works? > > Happy and safe New Year’s Eve! > > Kent > > _______________________________________________ > netmod mailing list > netmod@ietf.org > https://www.ietf.org/mailman/listinfo/netmod -- Ladislav Lhotka <ladis...@lhotka.name> PGP Key ID: 0xB8F92B08A9F76C67 _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
