Fix incorrect OpenAPI definition when using FromForm with IEnumerable #64925
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.
Fix incorrect OpenAPI schema for single [FromForm] collections
Wrap single [FromForm] IEnumerable parameters in an object schema.
Description
This PR fixes a bug in the OpenAPI document generation where a single IEnumerable parameter decorated with [FromForm] was incorrectly serialized as a raw JSON array at the root of the request body.
Because application/x-www-form-urlencoded and multipart/form-data are key-value based formats, a collection must be associated with a field name (key). Previously, the logic identified IEnumerable types as "Complex Types" but failed to recognize that they cannot function as the root schema of a form, unlike POCOs.
Changes:
Added logic to GetFormRequestBody to detect IEnumerable types (excluding string).
Ensured that these collection types are always treated as properties of the form object rather than being assigned to the root complexTypeSchema.
Fixes #62328