Dashes in get param value is not accepted
See original GitHub issue@Get('/:uuid/stuff') public getSomething(@Param('uuid') uuid) { }
When i use the above, and sent a /1234-234234-24324234/stuff (as example)
I get a ‘Error’ @ HttpError.js:18:22
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Can hyphens be used in query string values? - Stack Overflow
yes hyphens can be used . only characters can reliably use for the actual name parts of a URL are a-z, A-Z, 0-9,...
Read more >[QUESTION] query parameters with dashes instead ... - GitHub
In PyCharm I'm getting an error declaring my view parameters as such: "Illegal target for variable annotation". Realize this isn't FastAPI's ...
Read more >Dash (Hyphen) or Underscore in URLs: Which one to use and ...
Whether to use dashes or underscores in a URL depends on which part of ... parameter name (utm_campaign) and a query parameter value...
Read more >Accepting hyphenated query string parameter - CodeProject
I have a redirect to my API, the order-id is hyphenated, but my C# REST API accept order_id with underscore, how do I...
Read more >Options — Click Documentation (8.1.x)
The most basic option is a value option. These options accept one argument which is a value. If no type is provided, the...
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

Hi, I wanted to fix the bug but it turned about that it is a JSON.parse syntax error (caused by the dash) since the string will be treated as an object if you don’t specify the type. So if you specify that uuid is a string you wont get the error @thijsvanbuuren
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.