-
Notifications
You must be signed in to change notification settings - Fork 5.3k
java mgmt, typespec config #34522
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
base: main
Are you sure you want to change the base?
java mgmt, typespec config #34522
Conversation
Next Steps to MergeNext steps that must be taken to merge this PR:
|
PR validation pipeline started successfully. If there is ApiView generated, it will be updated in this comment. |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
|
maybe some problem in service's example JSON? |
It's due to truncated generated model test name resulting in duplicate class name (previously we fixed mock test duplication, though model test has this issue as well..). Fixed in microsoft/typespec#7282 |
SDK configuration pull request
Purpose of this PR
Align with Swagger config, and avoid name too long.
https://github.com/Azure/azure-rest-api-specs/blob/main/specification/recoveryservicesdatareplication/resource-manager/readme.java.md
Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:
tspconfig.yaml
templates:Getting help
Purpose of this PR
andDue diligence checklist
.write access
per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Merge
comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.queued
state, please add a comment with contents/azp run
.This should result in a new comment denoting a
PR validation pipeline
has started and the checks should be updated after few minutes.