Manuel Spigolon

Are you in a sync or async handler?

Old issue but still actual for me. I solved by running ``` yarn add --dev typescript@~4.3.2 ``` since `4.4.x` trigger this issue

This feature could be adapted to be used on `workspaces` too. ``` npm run-parallel lint --workspaces ``` executes in parallel the `lint` script for each project in the monorepo.

This feature assumes that the client calls sequentially the server, moreover, the client must be configured to don't rise a timeout on its side and the net stuff in the...

To replicate the issue you need to restore this commit: https://github.com/fastify/fastify-cli/pull/446/commits/56dcb64020e5a39820c9d8f826859949de880edc The scope of this issue is to use `fastify-cli/helper` instead of other stuff. If it is working now, it...

Hi all, I think this feature is a must-have in order to avoid "out-of-range" update that can't be merged (and get a notification flooding update). Checking the code, the function...

> The matter appears to be settled. I tried to reproduce it but I don't have any errors. Does anybody still have that problem? I think a test for this...

this schema works: ``` const stringify = fastJson({ anyOf: [schemaFoo, schemaBar] }) ``` Defining the `type` beside the `anyOf` would conflict when your data could be an object or a...

> is there any support for discriminated union types? As a general rule, I suggest running the [debugMode](https://github.com/fastify/fast-json-stringify#debug-mode) whenever there is some issue to understand what is going on. Debugging...

> discriminator keyword? No: it is a OpenAPI keyword and fast-json-stringify requires a JSON Schema Draft 7