Skip to content
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

[release/7.0] Do not generate Content for request parameters in OpenAPI #45439

Merged
merged 1 commit into from
Jan 4, 2023

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Dec 3, 2022

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?

  • Yes
  • No

Risk

  • High
  • Medium
  • Low

Low risk, because the impact area is restricted to users of the Microsoft.AspNetCore.OpenApi package and the WithOpenApi extension method. This change is not likely to have negative side effects since it updates the definition to be compliant with OpenAPI-requirements.

Verification

  • Manual (required)
  • Automated

Packaging changes reviewed?

  • Yes
  • No
  • N/A

@captainsafia captainsafia added the Servicing-consider Shiproom approval is required for the issue label Dec 5, 2022
@ghost
Copy link

ghost commented Dec 5, 2022

Hi @github-actions[bot]. Please make sure you've updated the PR description to use the Shiproom Template. Also, make sure this PR is not marked as a draft and is ready-to-merge.

To learn more about how to prepare a servicing PR click here.

@captainsafia
Copy link
Member

Approved via email.

@captainsafia captainsafia added Servicing-approved Shiproom has approved the issue and removed Servicing-consider Shiproom approval is required for the issue labels Dec 15, 2022
@ghost
Copy link

ghost commented Dec 15, 2022

Hi @github-actions[bot]. This PR was just approved to be included in the upcoming servicing release. Somebody from the @dotnet/aspnet-build team will get it merged when the branches are open. Until then, please make sure all the CI checks pass and the PR is reviewed.

@wtgodbe wtgodbe added this to the 7.0.3 milestone Jan 4, 2023
@wtgodbe wtgodbe merged commit 85f905e into release/7.0 Jan 4, 2023
@wtgodbe wtgodbe deleted the backport/pr-45404-to-release/7.0 branch January 4, 2023 18:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-web-frameworks Servicing-approved Shiproom has approved the issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants