-
Notifications
You must be signed in to change notification settings - Fork 325
[python] support multi-service scenario #9257
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
Conversation
- Update @azure-tools/azure-http-specs from 0.1.0-alpha.34-dev.7 to 0.1.0-alpha.34 - Update @typespec/http-specs from 0.1.0-alpha.30-dev.1 to 0.1.0-alpha.29 - Update @azure-tools/typespec-client-generator-core from ~0.63.0 to ~0.63.1 - Add service/multi-service to regenerate.ts configuration - Generate Python code for multi-service scenario - Add test_service_multi_service.py for sync tests - Add test_service_multi_service_async.py for async tests - Add changelog entry Co-authored-by: msyyc <[email protected]>
Co-authored-by: msyyc <[email protected]>
commit: |
|
All changed packages have been documented.
|
…ilot/update-http-client-dependencies
f4188e1 to
76e39ec
Compare
tadelesh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why we need to consider root client's API version in operation group? Can we always rely on operation group level's API version?
After offline discussion with @tadelesh , I replace |
fix #9030
In contrast to a single-service client, the root client provided by TCGC has an empty
apiVersionslist. Since an emptyapiVersionslist affects versioning validation and the client-level API version signature, this PR introduces two primary changes:rootClientApiVersionsto certain functions to enable accurate calculation of theaddedOnvalue, which is used for versioning validation.