Update Core tests with new DPG approach to ResponseClassifier #27279
Conversation
This file contains 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
annelo-msft
requested review from
JoshLove-msft,
christothes and
KrzysztofCwalina
as code owners
ghost
added
the
|
This pull request is protected by Check Enforcer. |
christothes
approved these changes
Mar 1, 2022
ShivangiReja
approved these changes
Mar 1, 2022
yanfa317
pushed a commit
to yanfa317/azure-sdk-for-net
that referenced
this pull request
Mar 8, 2022
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.
Per Azure/autorest.csharp#2006 (comment), DPG will change its approach to generating per-method ResponseClassifiers to use CoreResponseClassifier slightly differently than originally planned. This updates the tests in Core to validate that approach.