[Microsoft.StorageSync] Update .NET SDK to 7.0.0 to address swagger correctness changes#27271
Merged
ArthurMa1978 merged 3 commits intoAzure:mainfrom Mar 17, 2022
Conversation
Member
Author
|
@m-nash Could you please take a look at this PR? |
ArthurMa1978
approved these changes
Mar 17, 2022
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
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.
Summary of changes:
We recently had to fix our swagger spec to address completeness/correctness items in S360 (there were inconsistencies between live traffic and the swagger spec). To follow up on those fixes, we are updating our .NET SDK to reflect the updated spec for the 2020-09-01 API version (that's the version the .NET SDK is currently using).
Two rounds of swagger fixes were performed:
Azure/azure-rest-api-specs#16041
Azure/azure-rest-api-specs#17159
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.