API path with same prefix as base path is incorrectly double-normalized
Issue #129
resolved
e.g. if the base path is /test and the API operation path is /test123, the API path is incorrectly normalised to /123 and so a request to /test/test123 is never matched.
See #40 for discussion of the problem.
Comments (4)
-
-
reporter
Hmm. That’s odd. You should be able to… Is the repo marked as a fork of this one?
-
Got a PR created now (found out a workaround to create the PR
, see details below) : https://bitbucket.org/atlassian/swagger-request-validator/pull-requests/390/bugfix-fix-path-double-normalized-if-same
@James Navin It is marked as a fork of this one. But the create PR button is greyed out and tells me it is not possible.
Luckily I now found a “workaround” to make it work. I have to create the PR starting on my fork. Then I can select the original repository to create the fork for. Wonder if it will show up here then. We
Don’t think this is very intuitive and might be nice if this can also work from the source repository as I would have expected it 
-
reporter
- changed status to resolved
Available in 2.35.2
- Log in to comment
I have fixed this bug in my fork: https://bitbucket.org/pboos/swagger-request-validator/commits/f1cc36b268ae8880961f256591a67c3326cb0967
Problem though is, that I can’t open a PR on this project. @James Navin , any reason why I don’t have permissions to open a PR?