JSON-Schema Faker VS class-validator

There’s also json-schema-faker which is pretty cool.

https://github.com/json-schema-faker/json-schema-faker

I built a CSV generator which I then use as a test data source for a dsv library on that principle and another API generator based on schema. Something that might be additionally helpful is json-schema-faker, as you can probably convert you primary record (DB schema) to json-schema then just generate tons of data.

I only know https://github.com/json-schema-faker/json-schema-faker for JS, not Java though.

Hell, i was using this one earlier today; just kills me that people think this is acceptable.

The payload object contains a reference to a JSON Schema object that describes the properties of the event. This allows the consumer to know exactly how to define the event when publishing or how to write code that consumes a subscribed event. There are even tools online that generate examples from JSON Schema (and vice versa).

The class-validator / class-transform looks really nice for formatting/validation but there is also joi. suretype is attractive since theoretically typeconv could generate jsonSchema for json-schema-faker and Open API docs.

I've been using Fake your JSON-Schemas! (json-schema-faker.js.org), but it does not consider if-then-else rules in its generation process.

You can learn more from the documentation here.

This is the request body when creating a new task. The IsString decorator provided by class-validator rejects all types other than strings, including undefined or null. The task name value object does not consider the possibility of values other than strings.

In this class, we are using the famous class-validator to decorate our request parameters. This way it is more clear how we are going to use our request object and everything.

We add validation using https://github.com/typestack/class-validator.

I will make sure we get this documented.

Also OP can check out class-transformer + class-validator if he want to properly instantiate objects and validate them with precise and verbose output of potential format errors. OP can even go the god tier way by setting up a custom RxJS operator that does that for him easily.

Start by installing the class-transformer and class-validator packages for dto validation (see more in the docs), sharp for image optimization, and the S3 client packages.

The description of the request body model in NestJS is similar to the description of Ditsmod models, but NestJS uses decorators provided by the utility class-validator. In NestJS, it is customary to name the request body model with the ending *Dto (this is an abbreviation of Data transfer object):

You could use Zod or Superstruct to validate the types of values, or use typestack/class-validator if it makes sense.

Also, title of before article was I made 1,000x faster TypeScript validator library, but today's benchmark is showing that typescript-json is maximum 6,500x times faster. It's just because I added a new library class-validator in the benchmark and it is much slower than previous zod. Of course, I've continuously tuned the performance, but it just improved the performance about 2x times only.