paths get url-encoded with next export and getStaticPaths

[meesvandongen]

Bug report

Describe the bug

Paths get url-encoded when using next export. This causes them to get double-encoded when live.

To Reproduce

test case: https://gitlab.com/meesvandongen/test-case-next-export

build & export the project, serve it and go to the relevant page:

• /test/path%20with%20spaces
  doesn't work
• /test/path%2520with%2520spaces
  works; because we encoded the percent in %20 (space), giving %2520

Expected behavior

The routes are exported without encoding.

Additional context

This behaviour is different from exportPathMap, where the behaviour was as desired.

[machineghost]

This bug is nearly a year old; if it's not going to get fixed, at the very least could someone please add some documentation saying "you can't URI encode in getStaticPaths"?

[BURROO]

Has there been some development on this? I am struggling to get a readable search, filter and sort query due to this issue. Is there another work around to include characters like a ',' or '+' in a query string?

[machineghost]

It's been over a year ... and still no one has added even a single sentence anywhere in the documentation saying anything to the effect of "Next.js routes, whether dynamic or not, can't have % characters in them." (or "can't be URI Encoded", or whatever the actual details are).

C'mon Next team: why do you hate new users of your framework so much that you can't explain how it works to them with one line of documentation? It would literally take you < 10 minutes to make the PR for this.

P.S. I would happily submit the PR myself, if I knew what the Next rules on encoding special characters in URLs actually were.

[thanhtutzaw]

Also cannot decode url ( %20 ) in next/link . Any Idea ?
Example
url thor route works
url the%20avengers route didn't work but path is already generated with the-avengers route so I can access with manual typing in url bar not from Link