json-editor

There is vm2 [0] for nodejs, but if you look at the issues there are escapes found occasionally, even some this year. I think it's too risky to run untrusted code on node. You could run a headless chrome using puppeteer, then run workerbox. But it's probably too much overhead for a server app. Oh, if you're making a form builder, I have to recommend json-editor [1]. It's not mine and I haven't actually used it just (I've only found really recently), but basically you give a JSONSchema and it will make a form for you, with validations and conditionals all built in. Might come in useful. 0. https://github.com/markwylde/vm2-process 1. https://github.com/jdorn/json-editor

We are using it at my current place of work with https://github.com/jdorn/json-editor to generate simple administrative UIs for backing configurations for non-technical users. It's not a fantastic UX but it works and it's fast to develop. The docs are sparse but for my money the format is relatively intuitive. I'd prefer to be using XML/XSL/XSLT as they are FAR more powerful, but that's just what you get with JSON.

i've been happy with using Jeremy Dorn's as a start : https://github.com/jdorn/json-editor

It's pretty easy to extend JSON Schema with all sorts of other metadata about how a UI should represent the data, or how automated tools should interact with records, making your JSON Schema the single source of truth for your entire data model. The cool thing is that you can actualy write a JSON Schema that extends http://json-schema.org/schema which is the JSON Schema that describes JSON Schema, so you can validate that your use of your custom extensions to JSON Schema aren't misspelled or inconsistent. And that meta-schema can also be validated by http://json-schema.org/schema... It's schemas all the way down! Getting back to the point, my company is using this exact approach in production, with Python and client-side Javascript consuming the same schema. We have a React component that essentially does what https://github.com/jdorn/jso

I have some experience in this. Problem is, JSON Schema doesn't give you some attributes like order of properties for building the form. What makes sense is extending JSON Schema with optional properties that fill in things JSON Schema doesn't provide yet make it work with nothing but a JSON Schema. json-editor[1] does a very good job in this regard. Libraries like these are repeating what people have done already previously (classic JS framework DRY problem). They will need to solve a lot of corner cases to mature. Recursion, oneOf and some other JSON Schema properties are pretty hard to implement. [1] https://github.com/jdorn/json-editor

Hmm, so the types are not actually a part of the JSON output, but they live in a separate schema. That being the case, I would've preferred if this were built on top of http://json-schema.org/ instead of something entirely new and Python-specific. It seems like for the past couple of years JSON-schema has been just below some critical treshold for it to take off. Why not define models with JSON schema instead of a custom format for each web framework? Why not use JSON schemas to build forms, validation logic and admin interfaces, like https://github.com/jdorn/json-editor does? Why not document your API by specifying the JSON schema a GET request returns? (http://raml.org/ sort of does this). Seems like a chicken and egg problem where currently the tools are not yet nice enough to merit widespread adoption, but with widespread adoption the

Project page: https://github.com/jdorn/json-editor

The repo is here: https://github.com/jdorn/json-editor A working demo (although also on rawgit): http://rawgit.com/jdorn/json-editor/master/examples/css_inte...