\n\n# Stop typing twice ????♂️\n\nA lot of projects use JSON schemas for runtime data validation along with TypeScript for static type checking.\n\nTheir code may look like this:\n\n```typescript\nconst dogSchema = {\n type: \"object\",\n properties: {\n name: { type: \"string\" },\n age: { type: \"integer\" },\n hobbies: { type: \"array\", items: { type: \"string\" } },\n favoriteFood: { enum: [\"pizza\", \"taco\", \"fries\"] },\n },\n required: [\"name\", \"age\"],\n};\n\ntype Dog = {\n name: string;\n age: number;\n hobbies?: string[];\n favoriteFood?: \"pizza\" | \"taco\" | \"fries\";\n};\n```\n\nBoth objects carry similar if not exactly the same information. This is a code duplication that can annoy developers and introduce bugs if not properly maintained.\n\nThat's when `json-schema-to-ts` comes to the rescue ????\n\n## FromSchema\n\nThe `FromSchema` method lets you infer TS types directly from JSON schemas:\n\n```typescript\nimport { FromSchema } from \"json-schema-to-ts\";\n\nconst dogSchema = {\n type: \"object\",\n properties: {\n name: { type: \"string\" },\n age: { type: \"integer\" },\n hobbies: { type: \"array\", items: { type: \"string\" } },\n favoriteFood: { enum: [\"pizza\", \"taco\", \"fries\"] },\n },\n required: [\"name\", \"age\"],\n} as const;\n\ntype Dog = FromSchema;\n// => Will infer the same type as above\n```\n\nSchemas can even be nested, as long as you don't forget the `as const` statement:\n\n```typescript\nconst catSchema = { ... } as const;\n\nconst petSchema = {\n anyOf: [dogSchema, catSchema],\n} as const;\n\ntype Pet = FromSchema;\n// => Will work ????\n```\n\nThe `as const` statement is used so that TypeScript takes the schema definition to the word (e.g. _true_ is interpreted as the _true_ constant and not widened as _boolean_). It is pure TypeScript and has zero impact on the compiled code.\n\nIf you don't mind impacting the compiled code, you can use the `asConst` util, which simply returns the schema while narrowing its inferred type.\n\n```typescript\nimport { asConst } from \"json-schema-to-ts\";\n\nconst dogSchema = asConst({\n type: \"object\",\n ...\n});\n\ntype Dog = FromSchema;\n// => Will work as well ????\n```\n\nSince TS 4.9, you can also use the `satisfies` operator to benefit from type-checking and autocompletion:\n\n```typescript\nimport type { JSONSchema } from \"json-schema-to-ts\";\n\nconst dogSchema = {\n // Type-checked and autocompleted ????\n type: \"object\"\n ...\n} as const satisfies JSONSchema\n\ntype Dog = FromSchema\n// => Still work ????\n```\n\nYou can also use this with JSDocs by wrapping your schema in `/** @type {const} @satisfies {import('json-schema-to-ts').JSONSchema} */ (...)` like:\n\n```\nconst dogSchema = /** @type {const} @satisfies {import('json-schema-to-ts').JSONSchema} */ ({\n // Type-checked and autocompleted ????\n type: \"object\"\n ...\n})\n\n/** @type {import('json-schema-to-ts').FromSchema} */\nconst dog = { ... }\n```\n\n## Why use `json-schema-to-ts`?\n\nIf you're looking for runtime validation with added types, libraries like [yup](https://github.com/jquense/yup), [zod](https://github.com/vriad/zod) or [runtypes](https://github.com/pelotom/runtypes) may suit your needs while being easier to use!\n\nOn the other hand, JSON schemas have the benefit of being widely used, more versatile and reusable (swaggers, APIaaS...).\n\nIf you prefer to stick to them and can define your schemas in TS instead of JSON (importing JSONs `as const` is not available yet), then `json-schema-to-ts` is made for you:\n\n- ✅ **Schema validation** `FromSchema` raises TS errors on invalid schemas, based on [DefinitelyTyped](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/json-schema)'s definitions\n- ✨ **No impact on compiled code**: `json-schema-to-ts` only operates in type space. And after all, what's lighter than a dev-dependency?\n- ???? **DRYness**: Less code means less embarrassing typos\n- ???? **Real-time consistency**: See that `string` that you used instead of an `enum`? Or this `additionalProperties` you confused with `additionalItems`? Or forgot entirely? Well, `json-schema-to-ts` does!\n- ???? **Reliability**: `FromSchema` is extensively tested against [AJV](https://github.com/ajv-validator/ajv), and covers all the use cases that can be handled by TS for now\\*\n- ????️♂️ **Help on complex schemas**: Get complex schemas right first time with instantaneous typing feedbacks! For instance, it's not obvious the following schema can never be validated:\n\n```typescript\nconst addressSchema = {\n type: \"object\",\n allOf: [\n {\n properties: {\n street: { type: \"string\" },\n city: { type: \"string\" },\n state: { type: \"string\" },\n },\n required: [\"street\", \"city\", \"state\"],\n },\n {\n properties: {\n type: { enum: [\"residential\", \"business\"] },\n },\n },\n ],\n additionalProperties: false,\n} as const;\n```\n\nBut it is with `FromSchema`!\n\n```typescript\ntype Address = FromSchema;\n// => never ????\n```\n\n> \\*If `json-schema-to-ts` misses one of your use case, feel free to [open an issue](https://github.com/ThomasAribart/json-schema-to-ts/issues) ????\n\n## Table of content\n\n- [Installation](#installation)\n- [Use cases](#use-cases)\n - [Const](#const)\n - [Enums](#enums)\n - [Primitive types](#primitive-types)\n - [Nullable](#nullable)\n - [Arrays](#arrays)\n - [Tuples](#tuples)\n - [Objects](#objects)\n- [Combining schemas](#combining-schemas)\n - [AnyOf](#anyof)\n - [AllOf](#allof)\n - [OneOf](#oneof)\n - [Not](#not)\n - [If/Then/Else](#ifthenelse)\n - [Definitions](#definitions)\n - [References](#references)\n- [Deserialization](#deserialization)\n- [Extensions](#extensions)\n- [Typeguards](#typeguards)\n - [Validators](#validators)\n - [Compilers](#compilers)\n- [FAQ](#frequently-asked-questions)\n\n## Installation\n\n```bash\n# npm\nnpm install --save-dev json-schema-to-ts\n\n# yarn\nyarn add --dev json-schema-to-ts\n```\n\n> `json-schema-to-ts` requires TypeScript 4.3+. Using `strict` mode is required, as well as (apparently) turning off [`noStrictGenericChecks`](https://www.typescriptlang.org/tsconfig#noStrictGenericChecks).\n\n## Use cases\n\n### Const\n\n```typescript\nconst fooSchema = {\n const: \"foo\",\n} as const;\n\ntype Foo = FromSchema;\n// => \"foo\"\n```\n\n### Enums\n\n```typescript\nconst enumSchema = {\n enum: [true, 42, { foo: \"bar\" }],\n} as const;\n\ntype Enum = FromSchema;\n// => true | 42 | { foo: \"bar\"}\n```\n\nYou can also go full circle with typescript `enums`.\n\n```typescript\nenum Food {\n Pizza = \"pizza\",\n Taco = \"taco\",\n Fries = \"fries\",\n}\n\nconst enumSchema = {\n enum: Object.values(Food),\n} as const;\n\ntype Enum = FromSchema;\n// => Food\n```\n\n### Primitive types\n\n```typescript\nconst primitiveTypeSchema = {\n type: \"null\", // \"boolean\", \"string\", \"integer\", \"number\"\n} as const;\n\ntype PrimitiveType = FromSchema;\n// => null, boolean, string or number\n```\n\n```typescript\nconst primitiveTypesSchema = {\n type: [\"null\", \"string\"],\n} as const;\n\ntype PrimitiveTypes = FromSchema;\n// => null | string\n```\n\n> For more complex types, refinment keywords like `required` or `additionalItems` will apply ????\n\n### Nullable\n\n```typescript\nconst nullableSchema = {\n type: \"string\",\n nullable: true,\n} as const;\n\ntype Nullable = FromSchema;\n// => string | null\n```\n\n### Arrays\n\n```typescript\nconst arraySchema = {\n type: \"array\",\n items: { type: \"string\" },\n} as const;\n\ntype Array = FromSchema;\n// => string[]\n```\n\n### Tuples\n\n```typescript\nconst tupleSchema = {\n type: \"array\",\n items: [{ type: \"boolean\" }, { type: \"string\" }],\n} as const;\n\ntype Tuple = FromSchema;\n// => [] | [boolean] | [boolean, string] | [boolean, string, ...unknown[]]\n```\n\n`FromSchema` supports the `additionalItems` keyword:\n\n```typescript\nconst tupleSchema = {\n type: \"array\",\n items: [{ type: \"boolean\" }, { type: \"string\" }],\n additionalItems: false,\n} as const;\n\ntype Tuple = FromSchema;\n// => [] | [boolean] | [boolean, string]\n```\n\n```typescript\nconst tupleSchema = {\n type: \"array\",\n items: [{ type: \"boolean\" }, { type: \"string\" }],\n additionalItems: { type: \"number\" },\n} as const;\n\ntype Tuple = FromSchema;\n// => [] | [boolean] | [boolean, string] | [boolean, string, ...number[]]\n```\n\n...as well as the `minItems` and `maxItems` keywords:\n\n```typescript\nconst tupleSchema = {\n type: \"array\",\n items: [{ type: \"boolean\" }, { type: \"string\" }],\n minItems: 1,\n maxItems: 2,\n} as const;\n\ntype Tuple = FromSchema;\n// => [boolean] | [boolean, string]\n```\n\n> Additional items will only work if Typescript's `strictNullChecks` option is activated\n\n### Objects\n\n```typescript\nconst objectSchema = {\n type: \"object\",\n properties: {\n foo: { type: \"string\" },\n bar: { type: \"number\" },\n },\n required: [\"foo\"],\n} as const;\n\ntype Object = FromSchema;\n// => { [x: string]: unknown; foo: string; bar?: number; }\n```\n\nDefaulted properties (even optional ones) will be set as required in the resulting type. You can turn off this behavior by setting the `keepDefaultedPropertiesOptional` option to `true`:\n\n```typescript\nconst defaultedProp = {\n type: \"object\",\n properties: {\n foo: { type: \"string\", default: \"bar\" },\n },\n additionalProperties: false,\n} as const;\n\ntype Object = FromSchema;\n// => { foo: string; }\n\ntype Object = FromSchema<\n typeof defaultedProp,\n { keepDefaultedPropertiesOptional: true }\n>;\n// => { foo?: string; }\n```\n\n`FromSchema` partially supports the `additionalProperties`, `patternProperties` and `unevaluatedProperties` keywords:\n\n- `additionalProperties` and `unevaluatedProperties` can be used to deny additional properties.\n\n```typescript\nconst closedObjectSchema = {\n ...objectSchema,\n additionalProperties: false,\n} as const;\n\ntype Object = FromSchema;\n// => { foo: string; bar?: number; }\n```\n\n```typescript\nconst closedObjectSchema = {\n type: \"object\",\n allOf: [\n {\n properties: {\n foo: { type: \"string\" },\n },\n required: [\"foo\"],\n },\n {\n properties: {\n bar: { type: \"number\" },\n },\n },\n ],\n unevaluatedProperties: false,\n} as const;\n\ntype Object = FromSchema;\n// => { foo: string; bar?: number; }\n```\n\n- Used on their own, `additionalProperties` and/or `patternProperties` can be used to type unnamed properties.\n\n```typescript\nconst openObjectSchema = {\n type: \"object\",\n additionalProperties: {\n type: \"boolean\",\n },\n patternProperties: {\n \"^S\": { type: \"string\" },\n \"^I\": { type: \"integer\" },\n },\n} as const;\n\ntype Object = FromSchema;\n// => { [x: string]: string | number | boolean }\n```\n\nHowever:\n\n- When used in combination with the `properties` keyword, extra properties will always be typed as `unknown` to avoid conflicts.\n\n```typescript\nconst mixedObjectSchema = {\n type: \"object\",\n properties: {\n foo: { enum: [\"bar\", \"baz\"] },\n },\n additionalProperties: { type: \"string\" },\n} as const;\n\ntype Object = FromSchema;\n// => { [x: string]: unknown; foo?: \"bar\" | \"baz\"; }\n```\n\n- Due to its context-dependent nature, `unevaluatedProperties` does not type extra-properties when used on its own. Use `additionalProperties` instead.\n\n```typescript\nconst openObjectSchema = {\n type: \"object\",\n unevaluatedProperties: {\n type: \"boolean\",\n },\n} as const;\n\ntype Object = FromSchema;\n// => { [x: string]: unknown }\n```\n\n## Combining schemas\n\n### AnyOf\n\n```typescript\nconst anyOfSchema = {\n anyOf: [\n { type: \"string\" },\n {\n type: \"array\",\n items: { type: \"string\" },\n },\n ],\n} as const;\n\ntype AnyOf = FromSchema;\n// => string | string[]\n```\n\n`FromSchema` will correctly infer factored schemas:\n\n```typescript\nconst factoredSchema = {\n type: \"object\",\n properties: {\n bool: { type: \"boolean\" },\n },\n required: [\"bool\"],\n anyOf: [\n {\n properties: {\n str: { type: \"string\" },\n },\n required: [\"str\"],\n },\n {\n properties: {\n num: { type: \"number\" },\n },\n },\n ],\n} as const;\n\ntype Factored = FromSchema;\n// => {\n// [x:string]: unknown;\n// bool: boolean;\n// str: string;\n// } | {\n// [x:string]: unknown;\n// bool: boolean;\n// num?: number;\n// }\n```\n\n### OneOf\n\n`FromSchema` will parse the `oneOf` keyword in the same way as `anyOf`:\n\n```typescript\nconst catSchema = {\n type: \"object\",\n oneOf: [\n {\n properties: {\n name: { type: \"string\" },\n },\n required: [\"name\"],\n },\n {\n properties: {\n color: { enum: [\"black\", \"brown\", \"white\"] },\n },\n },\n ],\n} as const;\n\ntype Cat = FromSchema;\n// => {\n// [x: string]: unknown;\n// name: string;\n// } | {\n// [x: string]: unknown;\n// color?: \"black\" | \"brown\" | \"white\";\n// }\n\n// => Error will NOT be raised ????\nconst invalidCat: Cat = { name: \"Garfield\" };\n```\n\n### AllOf\n\n```typescript\nconst addressSchema = {\n type: \"object\",\n allOf: [\n {\n properties: {\n address: { type: \"string\" },\n city: { type: \"string\" },\n state: { type: \"string\" },\n },\n required: [\"address\", \"city\", \"state\"],\n },\n {\n properties: {\n type: { enum: [\"residential\", \"business\"] },\n },\n },\n ],\n} as const;\n\ntype Address = FromSchema;\n// => {\n// [x: string]: unknown;\n// address: string;\n// city: string;\n// state: string;\n// type?: \"residential\" | \"business\";\n// }\n```\n\n### Not\n\nExclusions require heavy computations, that can sometimes be aborted by Typescript and end up in `any` inferred types. For this reason, they are not activated by default: You can opt-in with the `parseNotKeyword` option.\n\n```typescript\nconst tupleSchema = {\n type: \"array\",\n items: [{ const: 1 }, { const: 2 }],\n additionalItems: false,\n not: {\n const: [1],\n },\n} as const;\n\ntype Tuple = FromSchema;\n// => [] | [1, 2]\n```\n\n```typescript\nconst primitiveTypeSchema = {\n not: {\n type: [\"array\", \"object\"],\n },\n} as const;\n\ntype PrimitiveType = FromSchema<\n typeof primitiveTypeSchema,\n { parseNotKeyword: true }\n>;\n// => null | boolean | number | string\n```\n\nIn objects and tuples, the exclusion will propagate to properties/items if it can collapse on a single one.\n\n```typescript\n// ???? Can be propagated on \"animal\" property\nconst petSchema = {\n type: \"object\",\n properties: {\n animal: { enum: [\"cat\", \"dog\", \"boat\"] },\n },\n not: {\n properties: { animal: { const: \"boat\" } },\n },\n required: [\"animal\"],\n additionalProperties: false,\n} as const;\n\ntype Pet = FromSchema;\n// => { animal: \"cat\" | \"dog\" }\n```\n\n```typescript\n// ❌ Cannot be propagated\nconst petSchema = {\n type: \"object\",\n properties: {\n animal: { enum: [\"cat\", \"dog\"] },\n color: { enum: [\"black\", \"brown\", \"white\"] },\n },\n not: {\n const: { animal: \"cat\", color: \"white\" },\n },\n required: [\"animal\", \"color\"],\n additionalProperties: false,\n} as const;\n\ntype Pet = FromSchema;\n// => { animal: \"cat\" | \"dog\", color: \"black\" | \"brown\" | \"white\" }\n```\n\nAs some actionable keywords are not yet parsed, exclusions that resolve to `never` are granted the benefit of the doubt and omitted. For the moment, `FromSchema` assumes that you are not crafting unvalidatable exclusions.\n\n```typescript\nconst oddNumberSchema = {\n type: \"number\",\n not: { multipleOf: 2 },\n} as const;\n\ntype OddNumber = FromSchema;\n// => should and will resolve to \"number\"\n\nconst incorrectSchema = {\n type: \"number\",\n not: { bogus: \"option\" },\n} as const;\n\ntype Incorrect = FromSchema;\n// => should resolve to \"never\" but will still resolve to \"number\"\n```\n\nAlso, keep in mind that TypeScript misses [refinment types](https://en.wikipedia.org/wiki/Refinement_type):\n\n```typescript\nconst goodLanguageSchema = {\n type: \"string\",\n not: {\n enum: [\"Bummer\", \"Silly\", \"Lazy sod !\"],\n },\n} as const;\n\ntype GoodLanguage = FromSchema<\n typeof goodLanguageSchema,\n { parseNotKeyword: true }\n>;\n// => string\n```\n\n### If/Then/Else\n\nFor the same reason as the `Not` keyword, conditions parsing is not activated by default: You can opt-in with the `parseIfThenElseKeywords` option.\n\n```typescript\nconst petSchema = {\n type: \"object\",\n properties: {\n animal: { enum: [\"cat\", \"dog\"] },\n dogBreed: { enum: Object.values(DogBreed) },\n catBreed: { enum: Object.values(CatBreed) },\n },\n required: [\"animal\"],\n if: {\n properties: {\n animal: { const: \"dog\" },\n },\n },\n then: {\n required: [\"dogBreed\"],\n not: { required: [\"catBreed\"] },\n },\n else: {\n required: [\"catBreed\"],\n not: { required: [\"dogBreed\"] },\n },\n additionalProperties: false,\n} as const;\n\ntype Pet = FromSchema;\n// => {\n// animal: \"dog\";\n// dogBreed: DogBreed;\n// catBreed?: CatBreed | undefined\n// } | {\n// animal: \"cat\";\n// catBreed: CatBreed;\n// dogBreed?: DogBreed | undefined\n// }\n```\n\n> ☝️ `FromSchema` computes the resulting type as `(If ∩ Then) ∪ (¬If ∩ Else)`. While correct in theory, remember that the `not` keyword is not perfectly assimilated, which may become an issue in some complex schemas.\n\n### Definitions\n\n```typescript\nconst userSchema = {\n type: \"object\",\n properties: {\n name: { $ref: \"#/definitions/name\" },\n age: { $ref: \"#/definitions/age\" },\n },\n required: [\"name\", \"age\"],\n additionalProperties: false,\n definitions: {\n name: { type: \"string\" },\n age: { type: \"integer\" },\n },\n} as const;\n\ntype User = FromSchema;\n// => {\n// name: string;\n// age: number;\n// }\n```\n\n> ☝️ Wether in definitions or references, `FromSchema` will not work on recursive schemas for now.\n\n### References\n\nUnlike run-time validator classes like [AJV](https://github.com/ajv-validator/ajv), TS types cannot withhold internal states. Thus, they cannot keep any identified schemas in memory.\n\nBut you can hydrate them via the `references` option:\n\n```typescript\nconst userSchema = {\n $id: \"http://example.com/schemas/user.json\",\n type: \"object\",\n properties: {\n name: { type: \"string\" },\n age: { type: \"integer\" },\n },\n required: [\"name\", \"age\"],\n additionalProperties: false,\n} as const;\n\nconst usersSchema = {\n type: \"array\",\n items: {\n $ref: \"http://example.com/schemas/user.json\",\n },\n} as const;\n\ntype Users = FromSchema<\n typeof usersSchema,\n { references: [typeof userSchema] }\n>;\n// => {\n// name: string;\n// age: string;\n// }[]\n\nconst anotherUsersSchema = {\n $id: \"http://example.com/schemas/users.json\",\n type: \"array\",\n items: { $ref: \"user.json\" },\n} as const;\n// => Will work as well ????\n```\n\n## Deserialization\n\nYou can specify deserialization patterns with the `deserialize` option:\n\n```typescript\nconst userSchema = {\n type: \"object\",\n properties: {\n name: { type: \"string\" },\n email: {\n type: \"string\",\n format: \"email\",\n },\n birthDate: {\n type: \"string\",\n format: \"date-time\",\n },\n },\n required: [\"name\", \"email\", \"birthDate\"],\n additionalProperties: false,\n} as const;\n\ntype Email = string & { brand: \"email\" };\n\ntype User = FromSchema<\n typeof userSchema,\n {\n deserialize: [\n {\n pattern: {\n type: \"string\";\n format: \"email\";\n };\n output: Email;\n },\n {\n pattern: {\n type: \"string\";\n format: \"date-time\";\n };\n output: Date;\n },\n ];\n }\n>;\n// => {\n// name: string;\n// email: Email;\n// birthDate: Date;\n// }\n```\n\n## Extensions\n\nIf you need to extend the JSON Schema spec with custom properties, use the `ExtendedJSONSchema` and `FromExtendedSchema` types to benefit from `json-schema-to-ts`:\n\n```typescript\nimport type { ExtendedJSONSchema, FromExtendedSchema } from \"json-schema-to-ts\";\n\ntype CustomProps = {\n numberType: \"int\" | \"float\" | \"bigInt\";\n};\n\nconst bigIntSchema = {\n type: \"number\",\n numberType: \"bigInt\",\n // ???? Ensures mySchema is correct (includes extension)\n} as const satisfies ExtendedJSONSchema;\n\ntype BigInt = FromExtendedSchema<\n CustomProps,\n typeof bigIntSchema,\n {\n // ???? Works very well with the deserialize option!\n deserialize: [\n {\n pattern: {\n type: \"number\";\n numberType: \"bigInt\";\n };\n output: bigint;\n },\n ];\n }\n>;\n```\n\n## Typeguards\n\nYou can use `FromSchema` to implement your own typeguard:\n\n```typescript\nimport { FromSchema, Validator } from \"json-schema-to-ts\";\n\n// It's important to:\n// - Explicitely type your validator as Validator\n// - Use FromSchema as the default value of a 2nd generic first\nconst validate: Validator = >(\n schema: S,\n data: unknown\n): data is T => {\n const isDataValid: boolean = ... // Implement validation here\n return isDataValid;\n};\n\nconst petSchema = { ... } as const\nlet data: unknown;\nif (validate(petSchema, data)) {\n const { name, ... } = data; // data is typed as Pet ????\n}\n```\n\nIf needed, you can provide `FromSchema` options and additional validation options to the `Validator` type:\n\n```typescript\ntype FromSchemaOptions = { parseNotKeyword: true };\ntype ValidationOptions = [{ fastValidate: boolean }]\n\nconst validate: Validator = <\n S extends JSONSchema,\n T = FromSchema\n>(\n schema: S,\n data: unknown,\n ...validationOptions: ValidationOptions\n): data is T => { ... };\n```\n\n`json-schema-to-ts` also exposes two helpers to write type guards. They don't impact the code that you wrote (they simply `return` it), but turn it into type guards.\n\nYou can use them to wrap either [`validators`](#validator) or [`compilers`](#compiler).\n\n### Validators\n\nA validator is a function that receives a schema plus some data, and returns `true` if the data is valid compared to the schema, `false` otherwise.\n\nYou can use the `wrapValidatorAsTypeGuard` helper to turn validators into type guards. Here is an implementation with [ajv](https://ajv.js.org/):\n\n```typescript\nimport Ajv from \"ajv\";\nimport { $Validator, wrapValidatorAsTypeGuard } from \"json-schema-to-ts\";\n\nconst ajv = new Ajv();\n\n// The initial validator definition is up to you\n// ($Validator is prefixed with $ to differ from resulting type guard)\nconst $validate: $Validator = (schema, data) => ajv.validate(schema, data);\n\nconst validate = wrapValidatorAsTypeGuard($validate);\n\nconst petSchema = { ... } as const;\n\nlet data: unknown;\nif (validate(petSchema, data)) {\n const { name, ... } = data; // data is typed as Pet ????\n}\n```\n\nIf needed, you can provide `FromSchema` options and additional validation options as generic types:\n\n```typescript\ntype FromSchemaOptions = { parseNotKeyword: true };\ntype ValidationOptions = [{ fastValidate: boolean }]\n\nconst $validate: $Validator = (\n schema,\n data,\n ...validationOptions // typed as ValidationOptions\n) => { ... };\n\n// validate will inherit from ValidationOptions\nconst validate = wrapValidatorAsTypeGuard($validate);\n\n// with special FromSchemaOptions\n// (ValidationOptions needs to be re-provided)\nconst validate = wrapValidatorAsTypeGuard<\n FromSchemaOptions,\n ValidationOptions\n>($validate);\n```\n\n### Compilers\n\nA compiler is a function that takes a schema as an input and returns a data validator for this schema as an output.\n\nYou can use the `wrapCompilerAsTypeGuard` helper to turn compilers into type guard builders. Here is an implementation with [ajv](https://ajv.js.org/):\n\n```typescript\nimport Ajv from \"ajv\";\nimport { $Compiler, wrapCompilerAsTypeGuard } from \"json-schema-to-ts\";\n\n// The initial compiler definition is up to you\n// ($Compiler is prefixed with $ to differ from resulting type guard)\nconst $compile: $Compiler = (schema) => ajv.compile(schema);\n\nconst compile = wrapCompilerAsTypeGuard($compile);\n\nconst petSchema = { ... } as const;\n\nconst isPet = compile(petSchema);\n\nlet data: unknown;\nif (isPet(data)) {\n const { name, ... } = data; // data is typed as Pet ????\n}\n```\n\nIf needed, you can provide `FromSchema` options, additional compiling and validation options as generic types:\n\n```typescript\ntype FromSchemaOptions = { parseNotKeyword: true };\ntype CompilingOptions = [{ fastCompile: boolean }];\ntype ValidationOptions = [{ fastValidate: boolean }];\n\nconst $compile: $Compiler = (\n schema,\n ...compilingOptions // typed as CompilingOptions\n) => {\n ...\n\n return (\n data,\n ...validationOptions // typed as ValidationOptions\n ) => { ... };\n};\n\n// compile will inherit from all options\nconst compile = wrapCompilerAsTypeGuard($compile);\n\n// with special FromSchemaOptions\n// (options need to be re-provided)\nconst compile = wrapCompilerAsTypeGuard<\n FromSchemaOptions,\n CompilingOptions,\n ValidationOptions\n>($compile);\n```\n\n## Frequently Asked Questions\n\n- [Does `json-schema-to-ts` work on _.json_ file schemas?](./documentation/FAQs/does-json-schema-to-ts-work-on-json-file-schemas.md)\n- [Will `json-schema-to-ts` impact the performances of my IDE/compiler?](./documentation/FAQs/will-json-schema-to-ts-impact-the-performances-of-my-ide-compiler.md)\n- [How can I apply `FromSchema` on generics?](./documentation/FAQs/applying-from-schema-on-generics.md)\n- [I get a `type instantiation is excessively deep and potentially infinite` error, what should I do?](./documentation/FAQs/i-get-a-type-instantiation-is-excessively-deep-and-potentially-infinite-error-what-should-i-do.md)\n","_attachments":{},"homepage":"https://github.com/ThomasAribart/json-schema-to-ts#readme","bugs":{"url":"https://github.com/ThomasAribart/json-schema-to-ts/issues"},"license":"MIT"}
![\"Theodo\"](\"https://github.com/theodo.png\")
![\"Plus](\"assets/plus-sign.png\")
Your BrandHere![](\"assets/header-round-medium.png\")
\n\n???? _Huge thanks to the [sponsors](https://github.com/sponsors/ThomasAribart) who help me maintain this repo:_\n\n