vesper8
commented
3 years ago Hey! Thanks for your comments : )
Yes I did give up on https://github.com/vue-generators/vue-form-generator which showed promise but appears to have been abandoned. I did find that the way they implement custom components lacked flexibility anyway.
I took a long look at other schema-based form generators and saw a whole lot that did things manually but none of them, in my opinion, showed as much promise and flexibility as https://github.com/jarvelov/vue-form-json-schema. On top of that it appears to be actively maintained and the author was helpful and responsive.
Most of all I wanted something where adding my own custom components would be relatively pain free and this one certainly checks that box. It is possible to build the entire dom with the schema alone as you saw, but this means having an extremely complex and verbose schema, instead I prefer to handle things like validation my way and use custom components that are more than a single html tag.
I have begun re-writing this UI (from this here package) using vue-form-json-schema but this is really only for a hobby project and I'm not sure if I will ever finish it. I am however now using vue-form-json-schema in production and it's working out quite well. I can certainly recommend it.
I felt like this generator was rather poorly done anyway, it certainly would be nice if a fully-featured UI was available to accompany vue-form-json-schema
Hi, I came across your comment about using props in JSON Form Schema and then I saw this UI. I've seen your name on some of the other discussions around schema-based form generators.
Did you give up om vue-form-generator because it's no longer maintained? That certainly has put me off!
I have been liking VueFormulate but they don't have support for logic in the schema for showing/hiding/requiring fields yet (although recently agreed to think about for next version).
I appreciated your comment in JSON Form Schema re: custom components, because that addresses something that annoyed me about that layer is how verbose the schema can become. I see how just using your own higher-order components can address that to a good extent: just use the schema to provide enough attributes to know to render your own component.
We build a lot of forms in my company using an admin, so this would help move things along to a PWA. I'll be sure to check out what you're working on if you open-source it! :)