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 validator will fail to resolve correct schema if request route is resolved as /users/:userId and specification has route /users/:user_id.
Since it is not really important for router variable names to match the ones in specification, we should compare path just on the basis of having variable there, ignoring its name completely.
The text was updated successfully, but these errors were encountered:
kibertoad
changed the title
More flexible patht resolution with regards to path parameters
More flexible path resolution with regards to path parameters
Apr 12, 2019
Currently validator will fail to resolve correct schema if request route is resolved as
/users/:userId
and specification has route/users/:user_id
.Since it is not really important for router variable names to match the ones in specification, we should compare path just on the basis of having variable there, ignoring its name completely.
The text was updated successfully, but these errors were encountered: