Serialization errors will be send to errorHandler

[int1ch]

I have found that fastify sometimes can throw errors not caught by errorHandler and it's difficult to understand where it comes from.

Reduced Example you can find in the committed test:
Response schema with required field throws an error from fast-json-stringify when a required field is not found.

fastify.get('/', {
    schema: {
      response: {
        200: {
          type: 'object',
          properties: {
            name: { type: 'string' }
          },
          required: ['name']
        }
      }
    }

  }, function (req, reply) {
    reply.code(200).send({ no: 'thing' })
  })

So I decided that it will be ok idea to send the captured error to errorHandler like validation error, and add a sign that the error comes from serialization.

But here I need your advice on how to envelop error propely.

Checklist

• run npm run test and npm run benchmark
• tests and/or benchmarks are included
• documentation is changed or added
• commit message and code follows the Developer's Certification of Origin
  and the Code of conduct

[mcollina]

lgtm

[mcollina]

Note that this has been refactored and improved in next, however this seems a very good fix.

[RafaelGSS]

LGTM.

[github-actions]

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.