-
Notifications
You must be signed in to change notification settings - Fork 8.8k
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
Dollar sign not works on copy / paste of curl command line #5390
Comments
Depending on the tradeoffs, it might be better to just always use singlequotes. |
per @hkosova:
|
Also, the "Add a backslash before '$'" solution is fine to me |
Yeah, perhaps we should just be using an escape library (a la Conveniently, we do build up an args array in our curlify function: swagger-ui/src/core/curlify.js Lines 4 to 9 in 9ea7fd9
|
This address a bug where a `$` character in a request body or header would not be properly escaped in a string in the generated curl command. Fixes swagger-api#5390
This address a bug where a `$` character in a request body or header would not be properly escaped in a string in the generated curl command. Fixes swagger-api#5390
This address a bug where a `$` character in a request body or header would not be properly escaped in a string in the generated curl command. Fixes swagger-api#5390
This address a bug where a `$` character in a request body or header would not be properly escaped in a string in the generated curl command. Fixes #5390
Content & configuration
I'm using swagger-ui to document an odata api
The curl command generated looks like this one :
Is your feature request related to a problem?
A copy / copy and paste of the following command line (on Unix based OS), the url will be interpreted as
https://myservice.net/odata/v4/Items?=3
Describe the solution you'd like
In order to make sure the dollar is not interpreted, it would be nice to have this kind of command line with parameter using single quote.
Describe alternatives you've considered
Otherwise dollar could be escaped, but I'm not sure it works under Windows :
Maybee using the url encoding code :
The text was updated successfully, but these errors were encountered: