-
Notifications
You must be signed in to change notification settings - Fork 1.5k
fix: support path level parameters for open_api_spec_parser #547
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
fix: support path level parameters for open_api_spec_parser #547
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
48b969b
to
777a292
Compare
777a292
to
34b0012
Compare
Hi @hangfei and @seanzhou1023 , i've fixed the unittest accordingly. |
Hi maintainers, just checking in on this PR. Let me know if any changes are needed or if there's anything I can do to help move it forward. Thanks! |
@seanzhou1023 Could you help review this change? |
lgtm, thanks for the fix :) |
autoformat the changes
Adding support of path level parameters in open_api_spec_parser as defined in the OpenAPI spec.
Ref: https://swagger.io/docs/specification/v3_0/describing-parameters/#common-parameters
This PR aimed in fixes #540 (*detailed problem description)
What this PR does
Proof that it works