[release/6.0] Add support for stating accepts/consumes metadata is required or not #36153
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
requested review from
BrennanConroy,
Pilchie,
Tratcher,
javiercn and
pranavkm
as code owners
davidfowl
approved these changes
Sep 3, 2021
ghost
added this to the
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #35875 to release/6.0
/cc @rafikiassumanimsft
Customer Impact
The changes will allow customers to use both Consumes attribute and Accepts extension method as a way to express the incoming request body type and content types for open API.
Testing
Unit tests.
Manual testing.
Risk
Low. This is a polish to an API and open API request description behaviors that we introduced in rc1.