Skip to content
New issue

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

More flexible path resolution with regards to path parameters #62

Closed
kibertoad opened this issue Apr 12, 2019 · 1 comment · Fixed by #74
Closed

More flexible path resolution with regards to path parameters #62

kibertoad opened this issue Apr 12, 2019 · 1 comment · Fixed by #74

Comments

@kibertoad
Copy link
Collaborator

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.

@kibertoad 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
@kobik kobik closed this as completed in #74 Jun 30, 2019
@manwithsteelnerves
Copy link

@kibertoad Can you please confirm if this is resolved? I noticed still its dependent on the parameter name format.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants