feat: support async constraint

[climba03003]

Add support for async constraints

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

[Uzlopak]

Does hasRoute need also some love?

[climba03003]

Does hasRoute need also some love?

There is no API changes in hasRoute or find-my-way.find

[climba03003]

CI failure due to Github Actions outage
https://www.githubstatus.com/incidents/gq1x0j8bv67v

I will re-run the CI after Github fix it.

[Uzlopak]

Github Actions run again properly
Restarted the failed CI

Code coverage is low

[mcollina]

lgtm

[climba03003]

@Fdawgs Do you have time to helps me check the document changes?

[Fdawgs]

Sorry @climba03003, missed this. Will take a look next week.

[Eomm]

Did you evaluate res.destroy instead?

The only difference is whether or not emit an error from the request object. Can't recall any other differences

[climba03003]

Not quite understand what you means.

[Eomm]

I needed to refresh this

const { fastify } = require('fastify')
const app = fastify()

app.get('/destroy', async (request, reply) => {
  reply.hijack()
  reply.raw.destroy('hello world')
})

app.get('/end', async (request, reply) => {
  reply.hijack()
  reply.raw.end('hello world')
})

app.inject('/end', check)
  .then(() => app.inject('/destroy', check))

function check (err, res) {
  console.log(err)
  console.log(res?.statusCode)
  console.log(res?.payload)
}

[climba03003]

.destory cannot and will not send any payload to the client. Instead, it close the socket immediately.
.end return a proper error message to the client and they can deal with it other than just wait for browser socket timeout.

[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.