Can you add an unit test for the changes?

It should be added in this folder https://github.com/fastify/fastify/tree/main/test/types

The change is already tested by this line.
https://github.com/rubybb/fastify/blob/907c2e274bb9cc77695add824a7f285df2f1b87c/test/types/hooks.test-d.ts#L99

Also we can add the hacktoberfest tag to this repository?
For more information: https://hacktoberfest.digitalocean.com/

If it's already tested there is no need for this change. I think it's a worthwhile change.

Can you add an unit test for the changes?
It should be added in this folder https://github.com/fastify/fastify/tree/main/test/types

The change is already tested by this line. https://github.com/rubybb/fastify/blob/907c2e274bb9cc77695add824a7f285df2f1b87c/test/types/hooks.test-d.ts#L99

Also we can add the hacktoberfest tag to this repository? For more information: https://hacktoberfest.digitalocean.com/

The test should be something like

expectType<string | undefined>(error.validationContext)

because the test you mention will always pass for any changes in FastifyError.

because the test you mention will always pass for any changes in FastifyError.

There is no check for any other properties in the error object, why should this one be unique?

because the test you mention will always pass for any changes in FastifyError.

There is no check for any other properties in the error object, why should this one be unique?

Test should be exist to ensure no regression in future. The current test is not enough for this purpose.

@RubyBB Can you fix the missing import for the test? I think it is the last pieces before merge.

Friendly ping @RubyBB

Would you like to push this PR over the line?

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.