We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
My paths are not being validated correctly with the new mux router.
Seems like the problem is here https://github.com/getkin/kin-openapi/blob/master/routers/gorillamux/router.go#L59
Any reason to not use the encoded path originally?
e.g.:
/my/pa%2Fram/path should match the route /my/{param}/path but it does not.
/my/pa%2Fram/path
/my/{param}/path
The text was updated successfully, but these errors were encountered:
Sounds like an issue specific to the encoding of / being %2F.
/
%2F
If you can use the originally encoded path and solve this issue for you I can help you with the pull request.
Sorry, something went wrong.
@fenollp Not sure I got exactly what you meant, but I got a PR working.
Successfully merging a pull request may close this issue.
Hi,
My paths are not being validated correctly with the new mux router.
Seems like the problem is here https://github.com/getkin/kin-openapi/blob/master/routers/gorillamux/router.go#L59
Any reason to not use the encoded path originally?
e.g.:
/my/pa%2Fram/path
should match the route/my/{param}/path
but it does not.The text was updated successfully, but these errors were encountered: