[release/7.0] Do not generate Content for request parameters in OpenAPI #45439
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.
Backport of #45404 to release/7.0
/cc @captainsafia
Do not generate Content for request parameters in OpenAPI
This PR addresses a bug where the OpenAPI generator produced incorrect definitions for parameters defined in headers/routes/queries/etc.
Fixes #45365
Customer Impact
Without this bug fix, the generated OpenAPI document is incorrect and users run into an underlying bug in Swagger UI that causes certain requests to hang the Swagger UI.
Regression?
Risk
Low risk, because the impact area is restricted to users of the
Microsoft.AspNetCore.OpenApi
package and theWithOpenApi
extension method. This change is not likely to have negative side effects since it updates the definition to be compliant with OpenAPI-requirements.Verification
Packaging changes reviewed?