-
Notifications
You must be signed in to change notification settings - Fork 98
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
Spec parser ignores response entries when there's an extension #165
Comments
zmay2030
pushed a commit
to zmay2030/spec
that referenced
this issue
Apr 19, 2023
zmay2030
pushed a commit
to zmay2030/spec
that referenced
this issue
Apr 19, 2023
Signed-off-by: Ahmad Moudani <ahmad.moudani@crowdstrike.com>
zmay2030
pushed a commit
to zmay2030/spec
that referenced
this issue
Apr 19, 2023
Signed-off-by: Aven <aven30@gmail.com>
zmay2030
pushed a commit
to zmay2030/spec
that referenced
this issue
Apr 19, 2023
Signed-off-by: Ahmad <aven30@gmail.com>
zmay2030
pushed a commit
to zmay2030/spec
that referenced
this issue
Apr 20, 2023
Signed-off-by: Ahmad Ma <aven30@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem statement
According to the OpenAPI Spec, OpenAPI Extensions are allowed to be under
responses
. But when loading the spec via load.Spec(), the response codes are completely ignored if there is an extension. If there is no extension, then the response codes are parsed and hydrated just fine.OpenAPI specification
OpenAPI Extensions
Steps to reproduce
Spec file (spec.json)
Code:
Output:
But when you remove the
"x-ext-resp": "response ext"
, it ends up dumping the following:Environment
swagger version:latest dev
go version: 1.19.1
OS: Mac
The text was updated successfully, but these errors were encountered: