Migrate cadl-ranch specs to http-specs and azure-http-specs #5204
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.
This is the azure part of Azure/azure-sdk-for-net#47325, and fix Azure/azure-sdk-for-net#47325
We split previous cadl-ranch tests into two parts: pure Typespec: http-specs, and Azure Typespec: azure-http-specs.
Now,
CadlRanchProjects
still means the code is generated under azure mode, no matter the spec is from http-specs or azure-http-specs.CadlRanchProjectsNonAzure
still means the code is generated under non-azure mode, no matter the spec is from http-specs or azure-http-specs.CadlRanchProjects.Tests
will generate reports for both azure and non-azure.CadlRanchProjectsNonAzure.Tests
will generate reports for both azure and non-azure.CadlRanchProjects.Tests
will be published to dashboard.