json-editor VS openapi-generator

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.

Generate TypeScript clients automatically

> Ideally I'd like to be able to write types in typescript, and write python types, then verify that the types are compatible (not identical)

Have a look at https://fastapi.tiangolo.com/

FastAPI allows you to define your types in Python using Pydantic for stronger type guarantees. FastAPI also generates an OpenAPI.json file for your backend and then you can feed this OpenAPI.json document into https://github.com/OpenAPITools/openapi-generator to generate a typescript library that contains all the types. Then you don't need to verify your types, because the typescript types will be directly generated from your Python types. The generated typescript library also contains methods for each of your REST endpoints, so that you don't have to think about network requests.

Patches are also useful if we're making manual modifications to any codebase that is being auto-generated, i.e. if we're using openapi-generator off of an OpenAPI spec to create clients and scaffolded server codebases. We would want to maintain the patch as a way to ensure that subsequent re-generations of the code don't wipe out any manual changes we have to make in-between.

The beta version was able to generate the expected Quote model object, but I ran into issues trying to generate an interface or abstract class that my controllers could extend. So I decided to create an issue in the openapi-generator library (link for those who are interested in the details) and pivot toward another approach.

Step 1: Locate the Right Template For Spring-based projects, navigate to: JavaSpring/ Key templates to modify: model.mustache → Handles imports pojo.mustache → Defines annotation

It would be great if D supported something like OpenAPI generator https://github.com/OpenAPITools/openapi-generator

Maybe it exists and I am just ignorant but it doesn't seem to be in the list of supported languages.

various openapi-generator plugins

OpenAPI Generator Gradle Plugin

I'm also really happy with spec first. We're using openapi-generator[1] to generate types from a yaml schema (inverting the more standard approach of generating the yaml) in our Typescript (mostly Nest.js) backends, and export those types as packages for use in our frontends.

[1] https://github.com/OpenAPITools/openapi-generator