-
Notifications
You must be signed in to change notification settings - Fork 668
Suggestion: url encode project paths automatically #1498
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
Comments
Hi @chris-peterson thanks, can you give some examples of endpoints that don't allow project paths to have Things like |
@nejch -- I am grateful that the get function will accept non-encoded project ids. the suggestion is for other APIs, e.g. updating a project. here's an example: works: fails: my workaround so far has been to either:
|
Thanks! I see, so this is mostly an issue with the CLI as with the API you would usually first get the object (even if lazily), but we should update this, it should be a few one-liners. Thanks for the report! Related to #1356 |
In the CLI we need to make sure the components put into the path portion of the URL are url-encoded. Otherwise they will be interpreted as part of the path. For example can specify the project ID as a path, but in the URL it must be url-encoded or it doesn't work. Also stop adding the components of the path as query parameters in the URL. Closes: #783 Closes: #1498
In the CLI we need to make sure the components put into the path portion of the URL are url-encoded. Otherwise they will be interpreted as part of the path. For example can specify the project ID as a path, but in the URL it must be url-encoded or it doesn't work. Also stop adding the components of the path as query parameters in the URL. Closes: #783 Closes: #1498
In the CLI we need to make sure the components put into the path portion of the URL are url-encoded. Otherwise they will be interpreted as part of the path. For example can specify the project ID as a path, but in the URL it must be url-encoded or it doesn't work. Also stop adding the components of the path as query parameters in the URL. Closes: #783 Closes: #1498
Description of the problem, including code/CLI snippet
Would be nice to not have to url-encode project paths when calling project APIs. Feels pretty safe to replace
/
with%2F
and not break folksExpected Behavior
Allow project paths to contain
/
without any escaping/encodingActual Behavior
Results in 404s, project not found. have to url encode and try again.
Specifications
The text was updated successfully, but these errors were encountered: