Set requiredness for primitive and files in forms #57196
Merged
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.
Closes #57112.
This PR updates the handling of required parameters within the form body to match the framework implementation.
OpenApiRequestBody.Requiredproperty is always set to true for forms. The framework does not support empty bodies for form-based requests in the same way that it does for JSON-based requests.OpenApiRequestBody.Content.Requiredproperty is updated to include required parameters of a primitive type in the list if they are required.[FromForm] Todo todo) is not affected by this change since the JsonSchemaExporter will set requiredness correctly for complex types.