fastify-racing VS fastify-swagger

Specifically, I noticed that the node mysql client can't cancel a running query and that the Fastify requestTimeout does something unrelated. It looks like I could use a 3rd party fastify-racing plugin to get an AbortController, but I'd need to wire that into my code in many places and I still wouldn't be able to cancel the SQL query.

With Speakeasy, you can create client SDKs based on an OpenAPI specification. Fastify ships with the @fastify/swagger plugin, which provides convenient shortcuts for generating good OpenAPI specifications. We'll start this tutorial by registering @fastify/swagger in a Fastify project to generate a spec.

First let’s get our current OpenAPI specification out of Fastify and onto the file system. If you have not added the https://github.com/fastify/fastify-swagger plugin first go do that. Then use this simple script I called generate-spec.ts to write your OpenAPI specification to the filesystem.

The fastify-swagger docs has an example https://github.com/fastify/fastify-swagger

@fastify/swagger is a fastify plugin to serve a Swagger UI, using Swagger (OpenAPI v2) or OpenAPI v3 schemas automatically generated from your route schemas, or from an existing Swagger/OpenAPI schema.

On the Node.js framework side of things, Fastify has support for Swagger with the fastify-swagger plugin.

With this approach, backend can be any programming languages that support OpenAPI or Swagger. Personally, I use fastify-swagger; but I can also be things like Python's FastAPI or Golang's Gin/Buffalo/Native.