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
oas-valdiator "in: query" is ok, when its actually path #79
Comments
Fixed case where this existing check was not being executed when the operation did not have any parameters of its own. The code is still done as part of the operation validation, so if the path has no operations (as literally in your example above) then it still won't flag as an error. I think that limitation is worth not duplicating the code for now. |
Thanks for a fix! I think the complete resolution to this would be having it check "Hey um you said this was in the query but uggghhhhh it's in the path..." |
It checks both ways, that all |
E.g. you can have the same parameter name in |
Ah, im just trying to figure out the discrepency between this validator and whatever Swagger Editor is doing. Folks keep raising concerns about Speccy when the answers from both systems are different. |
Fix above should resolve it, except in the case there are no operations at all on a path. |
Fantastic! Thank you :) |
Swagger Editor reports a semantic error for parameters which are marked as query but are defined in the URI template as part of the path.
Checklist
The text was updated successfully, but these errors were encountered: