Route params with special characters
See original GitHub issueIssue Description
There’s a way to pass attributes with some special caracters as params in routes? Something like “sl_bill.CD.PLP.100.2011”.
We use this format to our ids, but when I try to pass it as param I get an error.
Our route:
<Route path="/bill/:id" Component={Bill}>
The url will be something like this: localhost/bill/sl_bill.CD.PLP.100.2011
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
Characters allowed in GET parameter - Stack Overflow
Only alphanumerics, the special characters "$-_.+!*'(),", and reserved characters used for their reserved purposes may be used unencoded within a URL. The ...
Read more >About Routing with Express. We look at special characters ...
Some characters in string paths like ? , + , or * are special characters for paths with optional characters or wildcards. Placeholders...
Read more >Allowing Angular 4 Routes To Pass Special Characters In Url
Starter project for Angular apps that exports to the Angular CLI.
Read more >How to route get parameter special characters like * < >
How to route get parameter special characters like * < >. Route::get('/{nombre}', 'ArticuloController@show')->name('articulo');. ejemplo.test/dgdg*.
Read more >useRouter unable to fetch query params with special characters
useRouter unable to fetch query params with special characters. ... I was using useRouter to get the query params. Url example:
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
That error looks like it’s coming from webpack dev server, no?
It was a webpack problem guys, sry!
I found it here: https://github.com/webpack/webpack-dev-server/issues/454
I’ll close the issue.