-
-
Notifications
You must be signed in to change notification settings - Fork 435
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
Responses object doesn't support extensions #687
Comments
Correct! struct {
Extensions map[string]interface{} `json:"-"`
map[string]*ResponseRef `json:"responses"`
} with custom Un/MarshalJSON implementations. I'm in the middle of #513 but that work should make the fix for this issue easier. Also kin-openapi/openapi3/response.go Lines 31 to 33 in 46e0df8
21X and 2XX type fields...
|
fenollp
added a commit
to fenollp/kin-openapi
that referenced
this issue
Jan 23, 2023
Signed-off-by: Pierre Fenoll <[email protected]>
fenollp
added a commit
to fenollp/kin-openapi
that referenced
this issue
Feb 3, 2023
Signed-off-by: Pierre Fenoll <[email protected]>
fenollp
added a commit
to fenollp/kin-openapi
that referenced
this issue
Feb 14, 2023
Signed-off-by: Pierre Fenoll <[email protected]>
fenollp
added a commit
to fenollp/kin-openapi
that referenced
this issue
Mar 14, 2023
Signed-off-by: Pierre Fenoll <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
According to the OpenAPI Spec the
responses
object should be able to have extensions added to it https://spec.openapis.org/oas/v3.0.3#responses-objectThis object MAY be extended with [Specification Extensions](https://spec.openapis.org/oas/v3.0.3#specificationExtensions).
But the latest version of kin-openapi doesn't expose extensions for the
openapi3.Responses
type which at the moment looks to be just a type alias to a mapThe text was updated successfully, but these errors were encountered: