json-schema-to-ts VS json-schema-to-typescript

JSON Schema To TS

// First create a general "post" schema // Shared Schema export const postSchema = { $id: 'post', type: 'object', properties: { id: { type: 'number' }, title: { type: 'string' }, published: { type: 'boolean' }, content: { type: 'string' }, tags: { type: 'array', items: { type: 'string' } }, deleted: { type: 'boolean' } }, required: ['title', 'published', 'content', 'tags', 'deleted'] } as const // We don't need to create a separate "bodySchema". // But directly infer type from postSchema export type Body = FromSchema // Reply Schema // Check https://www.fastify.io/docs/latest/Reference/Validation-and-Serialization/#adding-a-shared-schema const replySchema = { type: 'object', properties: { posts: { type: 'array', items: { $ref: 'post#' } } }, additionalProperties: false } as const // Check https://github.com/ThomasAribart/json-schema-to-ts#references export type Reply = FromSchema< typeof replySchema, { references: [typeof postSchema] } > // Also make ReplyNotFound reusable for future use export const postNotFoundSchema = { $id: 'postNotFound', // add $id here type: 'object', required: ['error'], properties: { error: { type: 'string' } }, additionalProperties: false } as const export type PostNotFound = FromSchema

json-schema-to-ts comes to the rescue. 💪

https://github.com/ThomasAribart/json-schema-to-ts - Infers TS Types from raw JSON Schema object literals you embed in your code.

Fonte: https://github.com/ThomasAribart/json-schema-to-ts

Compile JSONSchema to TypeScript type declarations

Nice! Lots of tricky edge cases to do this right: there’s ambiguity in the JSON Schema spec, version-to-version changes, many popular community conventions that don’t adhere to the spec, etc. Feel free to check out the tests to understand some of these: https://github.com/bcherny/json-schema-to-typescript (shameless plug — I have maintained this library for a number of years).

jsonnet is my go-to language for anything related to configuration, after having tried json, yaml, TS, edn, and tasting dhall and toml. It addresses all problems in the article and more.

the composition strikes a good balance between extensiveness and ease of use.

the generated json leads to easy and portable data, and if you write jsonschemas from jsonnet, tools like json-schema-to-typescript [1] make it easy to import a consistent interface, and almost every language has a reasonably up-to-date validation library.

[1] https://github.com/bcherny/json-schema-to-typescript

Take a look at https://github.com/bcherny/json-schema-to-typescript, too. I used it successfully at a previous job. IIRC, I had to write some code to convert OpenAPI to JSON Schema but it wasn’t onerous

If you're using OpenAPI, you could use this to generate TypeScript interfaces:

https://github.com/bcherny/json-schema-to-typescript

It works really well

I'm messing around with a process to convert JSON schemas to TypeScript interfaces using json-schema-to-typescript. I have a little under 900 JSON files each containing a schema, totaling about 3.5 MB.

json-schema-to-typescript