-
Notifications
You must be signed in to change notification settings - Fork 76
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
Upgrade typespec compiler to v0.63 and cadl ranch spec to the latest #2942
Conversation
@@ -1069,49 +1067,6 @@ export function patientRecordArraySerializer( | |||
}); | |||
} | |||
|
|||
/** Provides status details for long running operations. */ | |||
export interface HealthInsightsOperationStatusError { | |||
/** The unique ID of the operation. */ |
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.
pls help investigate why the model is removed.
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.
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.
Is this a breaking for HLC? if so, could you create an issue in #2367
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.
I would assume no. Swagger side if the polling operation is exposed to public then during converting to tsp relevant models would be tagged with output usage and would include in modular.
Another thing is the health insight case in which we have nested result in body is not supported in hlc yet, so i would assume for this case the body type is directly exposed to public and its usage would be not limited to polling usage.
No description provided.