Fix for TSP lro-location-header rule
#28505
Closed
Conversation
This file contains 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
tjprescott
requested review from
weshaggard,
mikeharder and
konrad-jamrozik
as code owners
|
PR validation pipeline restarted successfully. This comment will be populated with next steps to merge this PR once validation is completed. Please wait ⌛. |
Swagger Validation Report
|
Swagger Generation Artifacts
|
|
PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment. |
tjprescott
force-pushed
the
tsp/LroLocationHeaderFix
branch
from
5c55b37 to
98ff451
Compare
tjprescott
added a commit
to Azure/typespec-azure
that referenced
this pull request
Mar 28, 2024
…Diff rule (#514) Closes Azure/typespec-azure-pr#3896 **REST API Specs** (9 violations) Azure/azure-rest-api-specs#28505 --------- Co-authored-by: Timothee Guerin <[email protected]>
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.
See: Azure/typespec-azure#514