You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the API docs on the website, testing any project slug (which requires a forward slash) into endpoints that takes a {slug} parameter shows a 404 error when the "Try" button is clicked to test the endpoint. The slash character is converted to "%2F" in the curl string shown, causing the project to be not found.
Expected behavior
Typing a project slug with a slash character and clicking Try should correctly test the endpoint.
slugs don't require a slash. we call "ViaVersion/ViaVersion" as namespace, where the first is the owner and the second part is the project slug. so you just want to put "ViaVersion" in there.
I guess we could be better at explaining the term slug, but its already documented for all endpoints that return a project
Observed/problematic behavior
In the API docs on the website, testing any project slug (which requires a forward slash) into endpoints that takes a {slug} parameter shows a 404 error when the "Try" button is clicked to test the endpoint. The slash character is converted to "%2F" in the curl string shown, causing the project to be not found.
Expected behavior
Typing a project slug with a slash character and clicking Try should correctly test the endpoint.
Steps to reproduce
Other
No response
The text was updated successfully, but these errors were encountered: