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
Hello,
Imagine I have the 2 routes in my API : /users/{userID:[^/]+} and /users/{userID:[^/]+}/books/{bookID:.+}.
The regexp are [^/]+ because without it, calling users/toto/books/openapi, matches with /users/{userID:[^/]+} with userID being toto/books/openapi.
The problem is that during Spec.SetupOperation(), {userID:[^/]+} is not matched by regexFindPathParameter ({([^}:]+)(:[^/]+)?(?:})).
I think changing the regex to {([^}:]+)(:[^}]+)?(?:}) would solve the problem.
The text was updated successfully, but these errors were encountered:
Hello,
Imagine I have the 2 routes in my API :
/users/{userID:[^/]+}
and/users/{userID:[^/]+}/books/{bookID:.+}
.The regexp are
[^/]+
because without it, callingusers/toto/books/openapi
, matches with/users/{userID:[^/]+}
with userID beingtoto/books/openapi
.The problem is that during
Spec.SetupOperation()
,{userID:[^/]+}
is not matched byregexFindPathParameter
({([^}:]+)(:[^/]+)?(?:})
).I think changing the regex to
{([^}:]+)(:[^}]+)?(?:})
would solve the problem.The text was updated successfully, but these errors were encountered: