一覧へ戻る
elierotenberg/fastify-zod（新しいタブで開きます）
主要言語: TypeScript
Zod integration with Fastify
- star 数
- 220
- watcher 数
- 3
- fork 数
- 24
- issue 数
- 17
- 最終更新
- 2024/02/27
gem-hunter主要言語: TypeScript
Zod integration with Fastify
fastify is awesome and arguably the best Node http server around.
zod is awesome and arguably the best TypeScript modeling / validation library around.
Unfortunately, fastify and zod don't work together very well. fastify suggests using @sinclair/typebox, which is nice but is nowhere close to zod. This library allows you to use zod as your primary source of truth for models with nice integration with fastify, fastify-swagger and OpenAPI typescript-fetch generator.
zod in a single place, without redundancy / conflicting sources of truthfastifyfastify-swagger and openapitools-generator/typescript-fetchenumfastify-zodnpm i fastify-zod
zodconst TodoItemId = z.object({ id: z.string().uuid(), }); enum TodoStateEnum { Todo = `todo`, InProgress = `in progress`, Done = `done`, } const TodoState = z.nativeEnum(TodoStateEnum); const TodoItem = TodoItemId.extend({ label: z.string(), dueDate: z.date().optional(), state: TodoState, }); const TodoItems = z.object({ todoItems: z.array(TodoItem), }); const TodoItemsGroupedByStatus = z.object({ todo: z.array(TodoItem), inProgress: z.array(TodoItem), done: z.array(TodoItem), }); const models = { TodoItemId, TodoItem, TodoItems, TodoItemsGroupedByStatus, };
fastify typesimport type { FastifyZod } from "fastify-zod"; // Global augmentation, as suggested by // https://www.fastify.io/docs/latest/Reference/TypeScript/#creating-a-typescript-fastify-plugin declare module "fastify" { interface FastifyInstance { readonly zod: FastifyZod<typeof models>; } } // Local augmentation // See below for register() const f = await register(fastify(), { jsonSchemas });
fastify-zod with optional config for fastify-swaggerimport { buildJsonSchemas, register } from "fastify-zod"; const f = fastify(); await register(f, { jsonSchemas: buildJsonSchemas(models), swaggerOptions: { // See https://github.com/fastify/fastify-swagger }, swaggerUiOptions: { // See https://github.com/fastify/fastify-swagger-ui }, transformSpec: {}, // optional, see below });
f.zod.post( `/item`, { operationId: `postTodoItem`, body: `TodoItem`, reply: `TodoItems`, }, async ({ body: nextItem }) => { /* body is correctly inferred as TodoItem */ if (state.todoItems.some((prevItem) => prevItem.id === nextItem.id)) { throw new BadRequest(`item already exists`); } state.todoItems = [...state.todoItems, nextItem]; /* reply is typechecked against TodoItems */ return state; } );
openapitools-generatorconst transformedSpecJson = await f .inject({ method: `get`, url: `/documentation_transformed/json`, }) .then((res) => res.body); await writeFile( join(__dirname, `..`, `..`, `openapi.transformed.json`), transformedSpecJson, { encoding: `utf-8` } );
openapitools-generatoropenapi-generator-cli generate
response instead of reply:f.zod.get( `/item/:id`, { operationId: `getTodoItem`, params: `TodoItemId`, response: { 200: `TodoItem`, 404: `TodoItemNotFoundError`, }, }, async ({ params: { id } }, reply) => { const item = state.todoItems.find((item) => item.id === id); if (item) { return item; } reply.code(404); return { id, message: `item not found`, }; } );
// Define custom messages const TodoItemId = z.object({ id: z.string().uuid("this is not a valid id!"), }); // Then configure fastify const f = fastify({ ajv: { customOptions: { allErrors: true, }, }, plugins: [require("ajv-errors")], }); await register(f, { jsonSchemas: buildJsonSchemas(models, { errorMessages: true }), });
buildJsonSchemas(models: Models, options: BuildJsonSchemasOptions = {}): BuildJonSchemaResult<typeof models>Build JSON Schemas and $ref function from Zod models.
The result can be used either with register (recommended, see example in tests) or directly with fastify.addSchema using the $ref function (legacy, see example in tests).
Record mapping model keys to Zod types. Keys will be used to reference models in routes definitions.
Example:
const TodoItem = z.object({ /* ... */ }); const TodoList = z.object({ todoItems: z.array(TodoItem), }); const models = { TodoItem, TodoList, };
BuildJsonSchemasOptions.$id: string = "Schemas": $id of the generated schema (defaults to "Schemas")BuildJsonSchemasOptions.target: jsonSchema7|openApi3 = "jsonSchema7": jsonSchema7 (default) or openApi3Generates either jsonSchema7 or openApi3 schema. See zod-to-json-schema.
The result of buildJsonSchemas has 2 components: an array of schemas that can be added directly to fastify using fastify.addSchema, and a $ref function that returns a { $ref: string } object that can be used directly.
If you simply pass the result to register, you won't have to care about this however.
const { schemas, $ref } = buildJsonSchemas(models, { $id: "MySchema" }); for (const schema of schemas) { fastify.addSchema(schema); } equals($ref("TodoItem"), { $ref: "MySchema#/properties/TodoItem", });
Shorthand to buildJsonSchema({ [$id]: Type }).schemas[0].
Add schemas to fastify and decorate instance with zod property to add strongly-typed routes (see fastify.zod below).
The result of buildJsonSchemas(models) (see above).
RegisterOptions<typeof models>.swaggerOptions = FastifyDynamicSwaggerOptions & { transformSpec: TransformSpecOptions }If present, this options will automatically register fastify-swagger in addition to fastify.zod.
Any options will be passed directly to fastify-swagger so you may refer to their documentation.
In addition to fastify-swagger options, you can pass an additional property, transformSpec, to expose a transformed version of the original spec (see below).
await register(f, { jsonSchemas: buildJsonSchemas(models), swaggerOptions: { swagger: { info: { title: `Fastify Zod Test Server`, description: `Test Server for Fastify Zod`, version: `0.0.0`, }, }, }, swaggerUiOptions: { routePrefix: `/swagger`, staticCSP: true, }, transformSpec: { /* see below */ }, });
If this property is present on the swaggerOptions, then in addition to routes added to fastify by fastify-swagger, a transformed version of the spec is also exposed. The transformed version is semantically equivalent but benefits from several improvements, notably first-class support for openapitools-generator-cli (see below).
cache caches the transformed spec. As SpecTransformer can be computationally expensive, this may be useful if used in production. Defaults to false.
routePrefix is the route used to expose the transformed spec, similar to the routePrefix option of fastify-swagger. Defaults to ${swaggerOptions.routePrefix}_transformed. Since swaggerOptions.routePrefix defaults to /documentation, then the default if no routePrefix is provided in either options is /documentation_transformed.
The exposed routes are /${routePrefix}/json and /${routePrefix}/yaml for JSON and YAML respectively versions of the transformed spec.
options are options passed to SpecTransformer.transform (see below). By default all transforms are applied.
Add route with strong typing.
Example:
f.zod.put( "/:id", { operationId: "putTodoItem", params: "TodoItemId", // this is a key of "models" object above body: "TodoItem", reply: { description: "The updated todo item", key: "TodoItem", }, }, async ({ params: { id }, body: item }) => { /* ... */ } );
Wraps fastify-swagger options providing a sensible default refResolver function compatible with using the $ref function returned by buildJsonSchemas`.
register automatically uses this under the hood so this is only required if you are using the result of buildJsonSchemas directly without using register.
SpecTransformer takes an API spec (typically the output of /openapi/json when using fastify-swagger) and applies various transforms. This class is used under the hood by register when swaggerOptions.transformSpec is set so you probably don't need to use it directly.
The transforms should typically be semantically transparent (no semantic difference) but applies some spec-level optimization and most importantly works around the many quirks of the typescript-fetch generator of openapitools-generator-cli.
SpecTransformer is a stateful object that mutates itself internally, but the original spec object is not modified.
Available transforms:
rewriteSchemasAbsoluteRefs transformTransforms $refs relative to a schema to refs relative to the global spec.
Example input:
{
"components": {
"schemas": {
"Schema": {
"type": "object",
"properties": {
"Item": {
/* ... */
},
"Items": {
"type": "array",
"items": {
// "#" refers to "Schema" scope
"$ref": "#/properties/Item"
}
}
}
}
}
}
}Output:
{
"components": {
"schemas": {
"Schema": {
"type": "object",
"properties": {
"Item": {
/* ... */
},
"Items": {
"type": "array",
"items": {
// "#" refers to global scope
"$ref": "#/components/schemas/Schema/properties/Item"
}
}
}
}
}
}
}extractSchemasProperties transformExtract properties of schemas into new schemas and rewrite all $refs to point to the new schema.
Example input:
{
"components": {
"schemas": {
"Schema": {
"type": "object",
"properties": {
"Item": {
/* ... */
},
"Items": {
"type": "array",
"items": {
"$ref": "#/components/schemas/Schema/properties/Item"
}
}
}
}
}
}
}Output:
{
"components": {
"schemas": {
"Schema": {
"type": "object",
"properties": {
"Item": {
"$ref": "#/components/schemas/Schema_TodoItem"
},
"Items": {
"$ref": "#/components/schemas/Schema_TodoItems"
}
}
},
"Schema_TodoItem": {
/* ... */
},
"Schema_TodoItems": {
"type": "array",
"items": {
"$ref": "#/components/schemas/Schema_TodoItem"
}
}
}
}
}mergeRefs transformFinds deeply nested structures equivalent to existing schemas and replace them with $refs to this schema. In practice this means deduplication and more importantly, referential equivalence in addition to structrural equivalence. This is especially useful for enums since in TypeScript to equivalent enums are not assignable to each other.
Example input:
{
"components": {
"schemas": {
"TodoItemState": {
"type": "string",
"enum": ["todo", "in progress", "done"]
},
"TodoItem": {
"type": "object",
"properties": {
"state": {
"type": "string",
"enum": ["todo", "in progress", "done"]
}
}
}
}
}
}
{
"mergeRefs": [{
"$ref": "TodoItemState#"
}]
}Output:
{
"components": {
"schemas": {
"TodoItemState": {
"type": "string",
"enum": ["todo", "in progress", "done"]
},
"TodoItem": {
"type": "object",
"properties": {
"state": {
"$ref": "#/components/schemas/TodoItemState"
}
}
}
}
}
}In the typical case, you will not create each ref explicitly, but rather use the $ref function provided by buildJsonSchemas:
{ mergeRefs: [$ref("TodoItemState")]; }
deleteUnusedSchemas transformDelete all schemas that are not referenced anywhere, including in paths. This is useful to remove leftovers of the previous transforms.
Example input:
{
"components": {
"schemas": {
// Schema_TodoItem has been extracted,
// there are no references to this anymore
"Schema": {
"type": "object",
"properties": {
"TodoItem": {
"$ref": "#/components/schemas/Schema_TodoItem"
}
}
},
"Schema_TodoItem": {
/* ... */
}
}
},
"paths": {
"/item": {
"get": {
"responses": {
"200": {
"content": {
"application/json": {
"schema": {
// This used to be #/components/Schema/properties/TodoItem
// but has been transformed by extractSchemasProperties
"$ref": "#/components/schemas/Schema_TodoItem"
}
}
}
}
}
}
}
}
}Output:
{
"components": {
"schemas": {
// "Schema" has been deleted
"Schema_TodoItem": {
/* ... */
}
}
},
"paths": {
/* ... */
}
}schemaKeys optionThis option controls the behavior of newly created schemas (e.g. during extractSchemasProperties transform).
Available configurations:
schemaKeys.removeInitialSchemasPrefix: remove schemaKey prefix of initial schemas to create less verbose schema names, e.g. TodoState instead of MySchema_TodoState
schemaKeys.changeCase: change case of generated schema keys. Defaults to preserve. In this case, original schema key and property key prefixes are preserved, and segments are underscore-separated.
In case of schema key conflict, an error will be thrown during transform.
Applies the given transforms.
Default options:
{ rewriteAbsoluteRefs?: boolean = true, extractSchemasProperties?: boolean = true, mergeRefs?: { $ref: string }[] = [], deleteUnusedSchemas?: boolean = true, schemaKeys?: { removeInitialSchemasPrefix: boolean = false, changeCase: "preserve" | "camelCase" | "PascalCase" | "snake_case" | "param-case" = "preserve" } = {} }
All transforms default to true except mergeRefs that you must explicitly configure.
Return the current state of the spec. This is typically called after transform to use the transformed spec.
Together with fastify-swagger, and SpecTransformer this library supports downstream client code generation using openapitools-generator-cli.
Recommended use is with register and fastify.inject.
For this you need to first generate the spec file, then run openapitools-generator:
const jsonSchemas = buildJsonSchemas(models); await register(f, { jsonSchemas, swaggerOptions: { openapi: { /* ... */ }, exposeRoute: true, transformSpec: { routePrefix: "/openapi_transformed", options: { mergeRefs: [$ref("TodoItemState")], }, }, }, }); const spec = await f .inject({ method: "get", url: "/openapi_transformed/json", }) .then((spec) => spec.json()); writeFileSync("openapi-spec.json", JSON.stringify(spec), { encoding: "utf-8" });
openapi-generator-cli generate
We recommend running this as part as the build step of your app, see package.json.
Unfortunately and despite best efforts by SpecTransformer, the OpenAPI generator has many quirks and limited support for some features. Complex nested arrays are sometimes not validated / parsed correctly, discriminated unions have limited support, etc.
MIT License Copyright (c) Elie Rotenberg