-
Notifications
You must be signed in to change notification settings - Fork 10.3k
[release/7.0] Don't generate RequestBody for parameters when disabledInferredBody is true #47807
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
Conversation
Hi @captainsafia. If this is not a tell-mode PR, please make sure to follow the instructions laid out in the servicing process document. |
Hi @captainsafia. 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. |
Looks like this PR hasn't been active for some time and the codebase could have been changed in the meantime. |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
Approved via email. |
Hi @captainsafia. 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. |
Description
The
disableInferredBody
configuration was not respected when generating the specification for theRequestBody
in the OpenAPI generator.Fixes #47644
Customer Impact
Without this bug fix, incorrect OpenAPI documents are produced for scenarios where customers are using certain parameter types in non-POST requests.
Regression?
Risk
The impact area of the bug is localized (
WithOpenApi
+ minimal APIs) so the risk is low.Verification
Packaging changes reviewed?