JSONForms VS zod

I'm currently working on an Android app that requires dynamic form creation based on JSON schema. I came across the website jsonforms.io and was impressed by their framework for generating forms from JSON schema.

We use JsonForms and for multiple forms and its quite powerful & consistant

There's this cool tool called JSON Forms. Basically you specify a schema and a rudimentary form is generated based on that schema with a framework of your choosing (vue, react, angular) with no additional configuration! Sounded cool so I cloned it. Now it looks like a real time saver, but i'm concerned about how I am using an 'imported template' that will probably restrict any customization on my end.

Json Forms: https://jsonforms.io/

Yes, exactly. I did some searching after I posed the question and found this so far https://jsonforms.io/

The best way I found to build form intensive apps is using: https://jsonforms.io/ It's super declarative with JSON Schema and can be easily extended by writing custom widgets. Also it provides good balance between being "battery charged" and freedom of state management.

I agree. RJSF examples work fine but it doesn't scale well to large forms. For a similar approach but better implementation, take a look at https://jsonforms.io/ which also supports multiple frameworks.

Of course in js there's a Library for that: https://jsonforms.io/

Zod is an open-source schema declaration and validation library that emphasizes TypeScript. It can refer to any data type, from simple to complex. Zod eliminates duplicative type declarations by inferring static TypeScript types and allows easy composition of complex data structures from simpler ones. It has no dependencies, is compatible with Node.js and modern browsers, and has a concise, chainable interface. Zod is lightweight (8kb when zipped), immutable, with methods returning new instances. It encourages parsing over validation and is not limited to TypeScript but works well with JavaScript as well.

Zod is a TypeScript-first schema declaration and validation library. It helps create schemas for any data type and is very developer-friendly. Zod has the functional approach of "parse, don't validate." It supports coercion in all primitive types.

Link: https://zod.dev/

You can check out their documentation here.

You can learn more about Zod on their website here.

In JS, it's a good idea anyway to use some JSON parsing library instead of JSON.parse.

With Zod, you can use z.bigint() parser. If you take the "parse any JSON" snippet https://zod.dev/?id=json-type and change z.number() to z.bigint(), it should do what you are looking for.

We will validate our input using client-side zod. Zod handles TypeScript-first schema validation with static type inference. This means that it will not only validate your fields, it will also set types on validated fields.

A word of warning: while discriminated unions are very powerful, there's an ongoing discussion on whether discriminated unions should be deprecated and replaced with a different API.

I was first introduced to Zod by Adam Bobrow - a colleague of mine and a dear friend. Adam was sick and tired from JavaScript's brittleness, and about two years ago he started migrating our code base to TypeScript. But that wasn't enough for him. He kept complaining: "What good are my types, if some other service decides to send me bad data and breaks my code?". That's when he discovered Zod.