[Python] Mitigate breaking changes for azure-mgmt-extendedlocation#7
Closed
ChenxiJiang333 wants to merge 1 commit intocxznmhdcxz:ruih/extendedlocation-tsp-convertfrom
Closed
Conversation
Next Steps to MergeImportant checks have failed. As of today they are not blocking this PR, but in near future they may.Addressing the following failures is highly recommended:
Comment generated by summarize-checks workflow run. |
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.
[Python] Mitigate breaking changes for azure-mgmt-extendedlocation
Mitigation Summary
CustomLocationstoExtendedLocationClient@@clientName(Microsoft.ExtendedLocation, "CustomLocationsMgmtClient", "python")to@@clientName(Microsoft.ExtendedLocation, "CustomLocations", "python")inclient.tspAccepted Breaking Changes (no mitigation needed)
These are expected TypeSpec migration changes handled by existing
@@Legacy.flattenPropertydecorators inback-compatible.tsp:CustomLocationOperation,PatchableCustomLocations,PatchableResourceSyncRule— flattened properties moved into nested objectsCustomLocationsOperations.update,ResourceSyncRulesOperations.begin_update— individual parameters replaced by singleparametersobjectCustomLocationOperationsListremoved (pageable behavior preserved)MatchExpressionsProperties.valuesrenamed tovalues_property(base model method conflict)