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
Currently openapi-core allows anything inside path parameters, as it uses the format parser to create regexes. This way the pattern /foo/{arg1} will match /foo/bar/baz. This is contrary to the openapi3 spec which disallows matches like this (as discussed e.g. OAI/OpenAPI-Specification#502)
What’s more troublesome, if we have two paths defined:
foo/{arg1}
foo/{arg1}/baz
Then whether the path foo/bar/baz matches the first one or the other depends on the order in which dictionary is iterated.
Is there any good reason we do this like that?
The text was updated successfully, but these errors were encountered:
Currently openapi-core allows anything inside path parameters, as it uses the format parser to create regexes. This way the pattern
/foo/{arg1}
will match/foo/bar/baz
. This is contrary to the openapi3 spec which disallows matches like this (as discussed e.g. OAI/OpenAPI-Specification#502)What’s more troublesome, if we have two paths defined:
foo/{arg1}
foo/{arg1}/baz
Then whether the path
foo/bar/baz
matches the first one or the other depends on the order in which dictionary is iterated.Is there any good reason we do this like that?
The text was updated successfully, but these errors were encountered: