Paste JSON as Code • quicktype VS typebox

Quicktype automates the generation of code from JSON data. It's a real timesaver when dealing with complex JSON structures in your applications.

Nice! JSON schemas are really useful, we use them a lot for code generation. Another library that does this for multiple languages is https://quicktype.io/ . It's great, but not so actively developed.

Quicktype is a speedy way to transform JSON data into well-structured, type-safe code in any programming language. Can help simplify the process of generating models and serializers from JSON, schema, or GraphQL—for secure, efficient data handling. 6-20PM finds it a "Godsend to convert JSON into data structures in any language."

Good candidate modules for these initial conversions are utility functions and code related to external APIs or specifications. It is possible to automatically generate TypeScript type definitions from Swagger contracts, GraphQL or JSON schemas to be included in your project. as well as you can use website called https://quicktype.io/ to generate types and interfaces in order to user them in your tsx or ts file.

Using Codable structs is better than dictionaries. Paste the JSON into https://quicktype.io/ and it will create the structs for you.

May be quicktype.io?

Check out quicktype.io. You can paste in your JSON and it will build your model for you. There's even an option for creating constructors. And you can choose your programming language. I usually spend some time cleaning it up a bit. It's not the perfect solution and I don't use it all the time, but it sure saves time for complicated models.

Hello. I used quicktype.io to try and implement an api in my code.

The documentation can be found here.

So far I like the commonly used approach in the Typescript community best:

1. Create your Schema using https://zod.dev or https://github.com/sinclairzx81/typebox

2. Generate your Types from the schema. It's very simple to create partial or composite types, e.g. UpdateModel, InsertModels, Arrays of them, etc.

3. Most modern Frameworks have first class support for validation, like is a great example Fastify (with typebox). Just reuse your schema definition.

That is very easy, obvious and effective.

There's a ton of schema validators out there and most devs have their personal favorite. Mine was zod and is now typebox + ajv.

If you're willing to document your API with an OpenAPI schema, then it should be possible to generate TypeScript types based on the OpenAPI schema with something like openapi-typescript. Also, Typebox can generate JSON schemas, maybe it can be used to generate something that the front-end can also use?

Well, I do provide extensibility for those bullet points you've listed to varying degrees (both schema and type representation), as well as offering a reference implementation for expressing a entirely different schema specification under the type system (specifically RFC8927 / JSON Type Definition). Reference implementation here. As for JSDoc, It's supported in code hints.

In setting out to build this service, we wanted to use gRPC for its APIs. We’ve been reaching for REST when building APIs so far, primarily out of necessity, i.e., our public APIs needed auto-generated client SDKs and docs for developers working with them. We built those APIs with Fastify and Typebox but felt burned by a code-first approach to generating an OpenAPI spec. I’ll spare you the details and save that experience/learning for another article. Suffice it to say we love gRPC’s schema-first approach. This blog post summarizes our feelings well