json-editor VS schema-dts

Combined with the fact that the parameter UI is highly dynamic through plugins(like how the extended choice parameters plugin supports defining complex input forms using json-editor means you can use Jenkins as an interface to run any kind of job that requires almost any type of input.

I use JSON schema to generate JSON-editing forms via json-editor: https://github.com/json-editor/json-editor

Then I can use the same schema in the backend to validate the data, both sent in via the form and directly with the application/json content-type. It's a pretty smooth flow, and reduces a lot of redundancy.

I have found stuff similar to this, for example json-editor.

JSON Editor takes a JSON Schema and uses it to generate an HTML form.

Some project followed that way like json-editor

json-editor is a really easy way to build complex forms. The resulting schema is returned as json which you can just convert to yaml. I use this in Jenkins for complex parameters.

https://github.com/json-editor/json-editor was used in the backbone.js version of swagger-ui to generate input forms from json-schema.

I'm trying to extract and validate json-ld objects from web pages but after a bunch of searching I cannot find any libraries that validate json-ld schema.org metadata that produces typed typescript objects. I was able to find schema-dts which has the typescript types, but does not appear to have a validator. I also found schemaorg-jsd, which does the validation, but does not seem to add typescript types to the object.

Just last week, I added the ability to export [Umami](https://www.umami.recipes/) recipes as [Recipe JSON Schema](https://schema.org/Recipe). Writing the code for it was quite pleasant thanks to [schema-dts](https://github.com/google/schema-dts).