Manuel Spigolon

Results 381 comments of Manuel Spigolon

We could support a `factory` option that will run for each request? ``` fastify.decorateRequest('array', function() { return [] }, { factory: true }) ```

> It's really objects, arrays, set and maps that are problematic. Agree on emitting a warning per these types

We have this repo to revamp https://github.com/fastify/fastify-citgm

Since yesterday you can: https://www.fastify.io/docs/latest/Reference/Request/#getvalidationfunction

Meanwhile, the user can write: ``` fastify.addSchema({ $id: 'foo' ... }) fastify.get('/', { schema: fastify.getSchema('foo') }, () => { const schema = fastify.getSchema('foo') }) ```

Overengineering time: a script that fetch the package.json for each module and read the `tags`. So the website will be able to filter by those (approved/filtered) tags

Go for it! I think we should change this function: https://github.com/fastify/fastify-express/blob/16cf8afe04b0d2406c7dc19f5e2cd77dbecd8f02/index.js#L54 providing a custom `next` callback to understand that express has ended its execution and apply the restore For sure...

@meehawk no, I mean this: ``` function runConnect (req, reply, next) { if (this[kMiddlewares].length > 0) { for (const [headerName, headerValue] of Object.entries(reply.getHeaders())) { reply.raw.setHeader(headerName, headerValue) } this.express(req.raw, reply.raw, customCallback)...

I think the logic that must be implemented to solve the failing tests is: given one single type `PageInfo`, the gateway's resolver function must choose to execute: 1. the simple...

@brandomeniconi I think to implement this logic https://github.com/mercurius-js/mercurius/pull/745#issuecomment-1057775819 The steps are: - when the gateway merges the same types `UserPage`, it should keep all the versions for each node -...