It builds on JSON schema and extends it in a number of useful ways. You provide a pair of functions to transform in each direction, calling the appropriate function when fetching, and then right before sending the editor contents back to the server. You can then perform transformations to/from that representation, as opposed to forcing your users to contend with a potentially awkward internally persisted representation. These editing representations can be made more intuitive, usable and less error-prone. You can base your schema on an ideal representation for editing, which may differ from the underlying storage representation.You prioritize which settings comes first, which are optional, etc. You can group related settings into separate schemas.You can freely manipulate the schema object in code, including transforming or augmenting it based on data you receive from the server-side, the user, etc. This makes it REALLY powerful and easy to use. This is enforced since this is the means with which the settings are updated. With settings schemas, it becomes part of your code, and will break if a setting name or data type change. Often wikis are created for this sort of thing, but they can quickly become out of date (or worse incorrect after changes). They allow you to provide human-readable names for your settings and provide documentation of the settings in the live system. This is where titles & descriptions in JSON schema really come in handy.

Settings can sometimes be given obtuse or confusing names. It solves a number of problems associated with the domain of app settings management: JSON schema is a standard for encoding the structure of JSON data. Using JSON schemas to model arbitrary data Without good administrative tools to both edit and check the correctness of settings updates, you can burden developers and chase issues with invalid data creeping into your system at runtime, rather than empowering the support and account management teams. But it becomes very important as you scale an application up and the number of settings you have begin to inevitably increase. In this blog post, IвЂ™m going to show how you can use the json-editor library to build these kinds of complex back-office admin apps really quickly and easily.Д¬onfigurable app settings management is often a neglected part of the product development process, typically cobbled together as a bare minimum effort. Building support for a large set of arbitrary data types, different editors for each, custom validation, etc. The settings have a flat unified structure in the back-end, making them awkward to manage logically as a set of related settings. For a long time, nobody tackled the task of properly exposing the management of these settings in a UI because they thought it would be way too much work. At work we have a lot of configurable settings in our application.

Json editor api