Wolfgang Hobmaier

I'd love to use fastify's validation since ajv precompiles these [into very efficient code](https://ajv.js.org/codegen.html) which is indeed a lot faster, but as you mentioned, we can use our validation layer...

Initial thought: I'd rather have 2 independent fastify templates. One with the tsoa validation service as a dependency, one without. But I'm not sure how much die duplication that implies,...

Can you please move this to the runtime package where it's actually being required? On second glance, I think we can reasonably just add it as a regular dependency.

What you suggested is a list of objects: `[ { $ref: '#/components/schemas/id' }, {description: Any description users like}]` This will not work unfortunately

You need decorators/reflection, but I am not sure why the snippet you referenced would need the emitted metadata

I don't know what the status is for esbuild on supporting decorators. My understanding is that emitDecoratorMetadata only adds additional information about the shape of the target which we don't...

You'd likely start off with a custom template and adapt that so can export a fastify plugin. E: See https://github.com/lukeautry/tsoa/tree/master/packages/cli/src/routeGeneration/templates

If we can cover it reasonably well in terms of integration tests and get them all green, sure!

@Kampfmoehre I'd be happy to add this as an "alpha" template so we can iterate without any stability presumptions. Would you be interested in sending a PR?

I'll happily guide you with the integration tests. You can open a PR without tests and I'll review it and give pointers. We probably only need fastify integration tests, but...