has field example seems wrong in next@canary

[gustavobini]

What version of Next.js are you using?

10.0.10-canary.11

What version of Node.js are you using?

12.2.0

What browser are you using?

Edge

What operating system are you using?

macOS

How are you deploying your application?

Not deploying

Describe the Bug

When following the recently added example provided in https://github.com/vercel/next.js/blob/canary/docs/api-reference/next.config.js/rewrites.md#header-cookie-and-query-matching for the has field with type query, the following error occurs when running next dev or next build:

`destination` has segments not in `source` (page) for route {"source":"/specific/:path*","has":[{"type":"query","key":"page","value":"home"}],"destination":"/:path*/:page"}

Expected Behavior

I am not entirely sure on this one. I would love if :page was accessible there but I believe the example is incorrect.

To Reproduce

npx create-next-app some-app

Create a next.config.js file in the root folder and add this content:

module.exports = {
  async rewrites() {
    return [
      {
        source: "/specific/:path*",
        has: [
          {
            type: "query",
            key: "page",
            value: "home",
          },
        ],
        destination: "/:path*/:page",
      },
    ];
  },
};

Run either next build or next start.

[laugharn]

#23588 doesn't appear to have fixed the example above that's also on https://nextjs.org/docs/api-reference/next.config.js/rewrites#header-cookie-and-query-matching

[gustavobini]

thanks @ijjk this is a very exciting feature and I truly hope it gets to stable version

[laugharn]

Yeah, I cannot wait for this!

[ijjk]

This should now be updated in v10.1.4-canary.9 of Next.js, please update and give it a try!

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.