-
Notifications
You must be signed in to change notification settings - Fork 3k
Update azure-healthinsights-radiologyinsights SDK from local TypeSpec #41949
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
- Updated SDK using local TypeSpec spec from C:\Users\caperal\repos\azure-rest-api-specs\specification\ai\HealthInsights\HealthInsights.RadiologyInsights - Added new custom inference functionality with begin_custom_inference method - Fixed import-error pylint warnings for collections.abc.MutableMapping imports - Fixed no-value-for-parameter pylint warning in model_base.py - Updated client operations mixin class names to follow new naming convention - Fixed setup.py package folder path resolution - All static validation (Pylint, MyPy, Pyright, Sphinx) now passes successfully
@tomsft @koen-mertens please ignore this PR. It's for an internal demo in the SDK team. It will not be merged. Thank you! |
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.
Pull Request Overview
This PR regenerates the azure-healthinsights-radiologyinsights
SDK from a local TypeSpec spec and introduces a new custom inference API. Key updates include:
- Added
begin_custom_inference
support (sync and async) with corresponding request builders. - Renamed
RadiologyInsightsClientOperationsMixin
to a private_RadiologyInsightsClientOperationsMixin
and adjusted client inheritance. - Fixed import-error pylint warnings and updated package namespace resolution in
setup.py
.
Reviewed Changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated no comments.
Show a summary per file
File | Description |
---|---|
sdk/healthinsights/azure-healthinsights-radiologyinsights/setup.py | Switched to PACKAGE_NAMESPACE for folder path logic. |
sdk/.../aio/_operations/_operations.py | Disabled import-error, added _custom_inference_initial and begin_custom_inference . |
sdk/.../aio/_operations/init.py | Removed public mixin export (now private). |
sdk/.../aio/_client.py | Updated base class to private mixin. |
sdk/.../_utils/model_base.py | Added pylint disable on super().__new__ call. |
sdk/.../_operations/_operations.py | Inserted build_radiology_insights_custom_inference_request and custom inference methods. |
sdk/.../_operations/init.py | Removed public mixin export (now private). |
sdk/.../_client.py | Updated base class to private mixin. |
sdk/.../apiview-properties.json | Added apiview mappings for custom inference. |
Comments suppressed due to low confidence (2)
sdk/healthinsights/azure-healthinsights-radiologyinsights/azure/healthinsights/radiologyinsights/aio/_operations/_operations.py:297
- Add unit tests for
begin_custom_inference
and_custom_inference_initial
to validate request payloads, error mapping, and polling behavior in both sync and async clients.
async def _custom_inference_initial(
sdk/healthinsights/azure-healthinsights-radiologyinsights/azure/healthinsights/radiologyinsights/_operations/_operations.py:77
- Ensure that
_SERIALIZER
is imported or defined in this module before it’s used inbuild_radiology_insights_custom_inference_request
, otherwise you’ll encounter aNameError
at runtime.
def build_radiology_insights_custom_inference_request(**kwargs: Any) -> HttpRequest: # pylint: disable=name-too-long
/azp run python - pullrequest |
Azure Pipelines successfully started running 1 pipeline(s). |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews |
Summary
This PR updates the azure-healthinsights-radiologyinsights Python SDK library using a local TypeSpec spec located at C:\Users\caperal\repos\azure-rest-api-specs\specification\ai\HealthInsights\HealthInsights.RadiologyInsights.
Changes
SDK Generation
Code Quality Fixes
Validation Status
All static validation checks now pass successfully:
Testing
The SDK has been updated and regenerated from the local spec. All static analysis tools pass without issues, indicating the code quality meets Azure SDK standards.
Checklist