Manuel Spigolon
Manuel Spigolon
> Is that a bad idea from a performance perspective? No, from the performance side. I would check the error case (such as client disconnected): if you don't handle it...
If you provide some inputs to the `deepmerge` func, something change?
> The first 9 parts are valid, and the 10th is invalid. We would then emit error. But we already piped the first 9 parts already somewhere. So there could...
It seems interesting, would you mind opening a PR with your code?
> How does it work without defining it? The listener's input definition doesn't change (still a single object) and the `.emit` wants an array too > Maybe just accept both...
friendly ping @andres-sm
I think it is due: As already said: this plugin does not need to be bumped for v5 (TBH: it would require a lot of effort and till it works...
I think that [`request.validateInput()`](https://fastify.dev/docs/latest/Reference/Request/#validate) replaces this (unused) module, so 👍🏼 on archiving it
TBH, if we can leverage AI to translate the website at build time it would be cool. Doing it manually leads to unmaintaned docs. eg: - Portuguese 5y without updates...
Switching the ajv version is as easy as writing: ``` const factoryValidator = require('@fastify/ajv-compiler')() const app = fastify({ schemaController: { compilersFactory: { buildValidator: factoryValidator } } }) ``` Since changing...