-
Notifications
You must be signed in to change notification settings - Fork 139
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
GET operations cannot have a request #546
Comments
caught by swagger editor! |
swagger-api/swagger-ui#2136 check out this issue, i don't think we should actually validate against this |
OAI/OpenAPI-Specification#2117 maybe we can warn instead |
From MDN:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/GET |
Happy to disallow it like conjure? |
I'm in favor of warning but allowing. |
Is there a use case where someone needs it? If certain server implementations don’t allow get bodies (per MDN) this could cause issues. Also a good place to encode an opinion. |
+1 to warn against having a Request in a GET body. |
+1 to this. |
* use axios-retry for retry logic * update sdk snapshots * pass in max retries * pass in max retries
Semantic error at the path (e.g. "paths./v2/link/provider/oauth/{oauth_provider}.get.requestBody")
GET operations cannot have a requestBody.
The text was updated successfully, but these errors were encountered: