[Python] TypeSpec migration for azure-mgmt-peering#45901
Draft
msyyc wants to merge 3 commits intoAzure:mainfrom
Draft
[Python] TypeSpec migration for azure-mgmt-peering#45901msyyc wants to merge 3 commits intoAzure:mainfrom
msyyc wants to merge 3 commits intoAzure:mainfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
TypeSpec Migration SDK Output for azure-mgmt-peering
Pre-migration swagger source
specification/peering/resource-manager @ 661ae882
Breaking Change Analysis
Mitigated (1)
Deleted or renamed model Enum0- Mitigated via@@clientName(CheckServiceProviderAvailabilityResponse, "Enum0", "python")in client.tspAccepted (19) - Parameters Changed to Keyword-only
All 19 parameter changes from
positional_or_keywordtokeyword_onlyare accepted per SDK guidelines (Category 9).Spec Mitigation PR
Azure/azure-rest-api-specs#41750