JSON Schema for Quasar?
First of all, loving Quasar!
We’d like to develop a JSON Schema to help express a Quasar template in JSON declarativly.
…which is brilliant, but ideally we’d go “full JSON Schema” in there with enums, titles, descirptions etc.
We’re happy to start writing one, based on quasar-helper-json.
Does anyone any thoughts on how best to proceed if it’s of benefit to the wider community (if at all!).
But thanks again all for Quasar, an amazing framework!
nothingismagick last edited by
You are not alone in this endeavor. At the moment there are at least two projects dealing exactly with this idea on the front end of Quasar, one project about building test harnesses into the backend of quasar and my own pet project - which is looking toward serving as a type of “bridge” between a single source of truth down to the quasar.conf.js and the individual components, routes and content.
At the following link you can see an outline that my project will take:
And here are some direct links to projects I briefly mentioned above:
- https://github.com/bloodf/Quasar-StoreRoutes (create routes from the store)
- https://github.com/tomers/vue-form-generator (is currently being patched to work with quasar)
Great, thank you for these links, they’re really interesting for what we’re doing (vue-form-generator especially).