-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Url Decoding #31
Comments
Hi, where do you want the decoded URL to appear? The problem with decoding is you can end up with invalid URLs, e.g. if the route is IMHO a client who consumes APIs should know what |
thnx for the answer lowest-rates?checkInDate=2015-12-07T09%3A29%3A18.130Z&checkOutDate=2015-12-08T09%3A29%3A18.131Z&codes=HT2%2C1121 these is a problem |
I see what you mean, it's not as easy to read as encodeURI('http://api.com/path?foo=ba r&message=hello:world')
// "http://api.com/path?foo=ba%20r&message=hello:world" I'll have a look to see where actually the URL gets encoded. |
Hi, can I use decoded url's when I generate the doc , because I have url's with parameters and I wont my client to ask me what this %20%
Thank you for your support
The text was updated successfully, but these errors were encountered: