Manuel Spigolon comments

Results 381 comments of


                                            Manuel Spigolon

Add documentation about errors thrown

Thanks for reporting! Would you like to send a Pull Request to address this issue? Remember to add unit tests.

feat: rendering the syntax of different content types responses

> Tests here will fail until the feature is merged at fastify, but I've hard-codded the fastify proposed changes and tested it. You can change&push temporary the package.json to use...

Disable accumulating files in memory while using attachFieldsToBody

Since this usage does not accumulate: ``` fastify.register(require('@fastify/multipart'), { attachFieldsToBody: true, onFile }) ``` I would support this new usage instead of adding a new option: ``` fastify.register(require('@fastify/multipart'), { attachFieldsToBody:...

remove dependency readable-stream

> Unfortunately I can not reproduce the issues on my local machine. Same error as the CI for me with node v18.6.0

Typescript: there is no way to make req.saveRequestFiles() works when we want to validate schema

Would you like to send a Pull Request to address this issue? Remember to add unit tests. cc @fastify/typescript

perf: replace querystring with fast-querystring

following the other prs https://github.com/fastify/fastify-reply-from/pull/272 Could you please add an option to configure the querystring module to use? Like in Fastify.

perf: replace querystring with fast-querystring

@mcollina I cannot release this package we should bump a major since there are 3 major versions that has been merged by automerge

move away from the .io TLD

Could we push forward this issue?

Adding shared schema in current encapsulated context

This can be done by a plugin. The scope of the fastify core is providing the minimal tool set to build things like the one you proposed. The plugin needs...

Serialize the response payload based on the content-type

Does this flow recap all the cases?