customRoutes will match full routes including query params

[moustacheful]

Description

Adding a customRoute which can receive query params will always fail since the match is done against the full URL, which includes the query params part.

What type of issue is this? (place an x in one of the [ ])

• bug
• enhancement (feature request)
• question
• documentation related
• example code related
• testing related
• discussion

Requirements (place an x in each of the [ ])

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.

---

Bug Report

Filling out the following details about bugs will help us solve your issue sooner.

Reproducible in:

package version: any

node version: any

OS version(s): any

Steps to reproduce:

1. Add a custom route
   This means adding something like:

    {
      path: '/say-hi',
      method: ['GET'],
      handler(req, res) {
        const params = qs.parse(req.url)
        res.end(`hello, ${params.name || 'world'}`)
      },
    }

2. Do a request against our shiny new route with query params
3. cry

Expected result:

What you expected to happen

curl localhost:3000/say-hi?name=doug%20dimmadome # hello, doug dimmadome

Actual result:

curl localhost:3000/say-hi?name=doug%20dimmadome # 404

[misscoded]

Hi @moustacheful! Great catch: we certainly overlooked this use case and this is definitely not the intended behavior. Thanks for not only providing us sufficient detail but for also opening a PR to introduce a fix! 🙏🏼

[seratch]

Fixed by #1207