Add OpenAPI :requestBody for :form request schema #703
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
OpenAPI Specification 3 requires defining form parameters, i.e. classic application/x-www-form-urlencoded type body as a :requestBody. They are not supported as regular parameters like in OAS 2.
opqdonut
approved these changes
Nov 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ring Coercion functionality allows defining a request schema with
{:parameters {:form some-schema}}. This resulted in that schema being transformed to OpenAPI parameters, which was supported in OAS 2 (Swagger), but is not supported in OAS 3. Now they must be defined as arequestBodyschema like any other kind of body.:formparameter coercion also implies that the request content type must beapplication/x-www-form-urlencoded.