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

[@azure-tools/azure-http-specs] - Remove handler for majority of the Scenarios #1691

Merged
merged 2 commits into from
Oct 16, 2024

Conversation

sarangan12
Copy link
Contributor

This is the continuation of the PR microsoft/typespec#4725. This PR handles the removal of handler property in majority of the Scenarios (Except ones related to LRO and that checks the absence of a parameter). All Scenarios are validated and tested. Please review and approve the PR. Thanks

@azure-sdk
Copy link
Collaborator

No changes needing a change description found.

@azure-sdk
Copy link
Collaborator

You can try these changes here

🛝 Playground 🌐 Website 📚 Next docs

@timotheeguerin timotheeguerin added this pull request to the merge queue Oct 16, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to a conflict with the base branch Oct 16, 2024
@sarangan12 sarangan12 enabled auto-merge October 16, 2024 16:39
@sarangan12 sarangan12 added this pull request to the merge queue Oct 16, 2024
Merged via the queue into Azure:main with commit 1505570 Oct 16, 2024
20 of 22 checks passed
@sarangan12 sarangan12 deleted the RemoveHandler branch October 16, 2024 17:41
markcowl pushed a commit to markcowl/typespec-azure that referenced this pull request Dec 5, 2024
…Scenarios (Azure#1691)

This is the continuation of the PR
microsoft/typespec#4725. This PR handles the
removal of handler property in majority of the Scenarios (Except ones
related to LRO and that checks the absence of a parameter). All
Scenarios are validated and tested. Please review and approve the PR.
Thanks
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.

3 participants