Next.js does not error when dynamic route segments re-use a name

[Timer]

Next.js does not throw an error for pages/[id]/[id].js, as reported on Spectrum.

[dfee]

Probably also worth mentioning, actual querystring params are clobbered by path-params.

i.e. /pages/[id1]/[id2].tsx called with /a/b?id1=c?id2=d?id3=e?id3=f returns =>

{ id1: 'a', id2: 'b', id3: ['e', 'f'] }

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