Manuel Spigolon

I was working on it too, I came up with this setup for an almost-nothing change except the time to lint ``` { "$schema": "https://biomejs.dev/schemas/1.3.3/schema.json", "organizeImports": { "enabled": true },...

I love this idea We could ship in v4 too, but the `namespace` prop could be dangerous so I would go with something like `pluginNamespace` and then `namespace` in v5....

I change my mind 😄 Let's see this real example: ```js test('plugin namespace', async t => { t.plan(2) const app = Fastify() await app.register(async function plugin (app, opts) { app.decorate('utility',...

> Also, maybe we can also work on centralizing all CI workflows (and possibly most scripts) during this release cycle We have centralized all the main extranal software such as...

A reminder that we have this notion page to see all the public repos and download stats: - https://eomm.notion.site/7a064537ee794af698684df68e215b54?v=a660ff01ca5344769a5f2b1a1c4eeda4&pvs=4

I think this issue belongs to: https://github.com/pinojs/pino-std-serializers Note that you can already implement this logic for a limited set of routes: https://fastify.dev/docs/latest/Reference/Routes/#custom-log-serializer > One example where this is extremely useful...

> Correct me if I'm wrong, but Fastify doesn't use pino's standard serializer for the request logger [1], so any changes made in pino wouldn't have any affect on this...

> What is the best way to redact req.url on a single route? There is an example you can be inspired of: set a context with a custom serializer for...

I like the `this` one

I think you are hitting this issue: https://github.com/fastify/fastify/blob/main/docs/Reference/Decorators.md#decoratereplyname-value-dependencies > In this example, the reference of the object is shared with all the requests: any mutation will impact all requests, potentially...