Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix ArmOperationStatus id type from Core.uuid to string #1759

Merged
merged 4 commits into from
Nov 1, 2024

Conversation

AlitzelMendez
Copy link
Member

issue: #1726

Copy link
Member

@markcowl markcowl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good. We should try a PR into the typespec-next branch of the azure-rest-api-specs repo to see how many specs are impacted. Let me know if you need help with this, the instructions are here: https://github.com/Azure/typespec-azure/blob/main/CONTRIBUTING.md#testing-a-change-in-repo-azure-rest-api-specs

@AlitzelMendez
Copy link
Member Author

@AlitzelMendez
Copy link
Member Author

I verified how to fix the v-next error, I just need to tsp compile to update the generated file, with all this information I feel confident about merging, so I will merge :)

@AlitzelMendez AlitzelMendez added this pull request to the merge queue Nov 1, 2024
Merged via the queue into Azure:main with commit e27b655 Nov 1, 2024
18 checks passed
@AlitzelMendez AlitzelMendez deleted the fix-arm-operation-status branch November 1, 2024 18:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: ArmOperationStatus id type does not match Azure-AsyncOperation Resource format
2 participants