Skip to content

add new features for Conversation Runtime #33086

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

Merged

Conversation

amber-ccc
Copy link
Member

@amber-ccc amber-ccc commented Mar 7, 2025

Choose a PR Template

Switch to "Preview" on this description then select one of the choices below.

Click here to open a PR for a Data Plane API.

Click here to open a PR for a Control Plane (ARM) API.

Click here to open a PR for only SDK configuration.

fix #33141

@amber-ccc amber-ccc requested a review from yangyuan as a code owner March 7, 2025 21:54
Copy link

openapi-pipeline-app bot commented Mar 7, 2025

Next Steps to Merge

✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.

Copy link

openapi-pipeline-app bot commented Mar 7, 2025

PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

@azure-sdk
Copy link
Collaborator

azure-sdk commented Mar 12, 2025

API Change Check

APIView identified API level changes in this PR and created the following API reviews

Language API Review for Package
TypeSpec Language.Conversations
TypeSpec Language.Text

@amber-ccc amber-ccc added the PublishToCustomers Acknowledgement the changes will be published to Azure customers. label Mar 13, 2025
@amber-ccc amber-ccc marked this pull request as ready for review March 18, 2025 18:07
@heaths
Copy link
Member

heaths commented Apr 9, 2025

Is this PR actually ready for review now? I've been ignoring it as long as its been in draft, unless you flag me specifically for questions.

@amber-ccc
Copy link
Member Author

Yes, this is ready for review now. Let me convert it.

@amber-ccc amber-ccc marked this pull request as ready for review April 9, 2025 19:19
@mikekistler
Copy link
Member

Please address @heaths and @johanste comments and then ping here so I can add the signedOff label.

@amber-ccc
Copy link
Member Author

Hi, @heaths , I have updated the code based on your comments, could you pls take a look and let me know? Thank you!

Copy link
Member

@heaths heaths left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume you've updated the service to match the cancelAfterSeconds?: int32 change as well?

@amber-ccc
Copy link
Member Author

amber-ccc commented Apr 10, 2025

Hi @heaths ,
For the change to cancelAfterSeconds?: int32, I just confirmed with my teammates that we received suggestions from the API review board. Since this is just a preview version, we can keep it as cancelAfter?: float32 for now until we get feedback from customers.
So I will restore this changes for now, do you agree with this? Thank you!

@heaths
Copy link
Member

heaths commented Apr 10, 2025

until we get feedback from customers

I doubt you will, but we provide this feedback to provide consistency and for their benefit. Our guidelines say to put a unit of time/measurement in their to make it self-descriptive.

@amber-ccc
Copy link
Member Author

Thanks for your suggestions, @heaths . For this part, I’m not working on the service side—I’m only handling the TypeSpec work based on service-side changes. So, I may need to keep the property as cancelAfter?: float32 to stay consistent with the service.

We’re planning to release GA at the end of April or early May. We will review the customers' feedback and talk about this point again.

@amber-ccc
Copy link
Member Author

amber-ccc commented Apr 10, 2025

Hi @mikekistler , I have addressed the comments and health has approved this PR, could you please add the signedOff label if everything looks good? Thank you.

Copy link
Member

@mikekistler mikekistler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. 👍

@mikekistler mikekistler added the APIStewardshipBoard-SignedOff The Azure API Stewardship team has reviewed and approved the changes. label Apr 14, 2025
@AzureRestAPISpecReview AzureRestAPISpecReview added VersioningReviewRequired <valid label in PR review process>add this label when versioning review is required and removed new-api-version labels Apr 16, 2025
@amber-ccc amber-ccc added BreakingChange-Approved-Benign Changes are not breaking at the REST API level and have at most minor impact to generated SDKs. Versioning-Approved-Benign https://github.com/Azure/azure-sdk-tools/issues/6374 labels Apr 16, 2025
@amber-ccc amber-ccc merged commit 417b5dc into Azure:main Apr 16, 2025
45 of 49 checks passed
danieljurek pushed a commit that referenced this pull request Apr 17, 2025
* added new request and response Type

* add version information for 2025_05_15

* adjust type to avoid breaking changes

* added testing files for conversation runtime 2025-05-15 and modified the readme

* revert to Typespec 0.66 version

* added comments for Conversations Runtime 2025-05-15

* fixed Typespec validation

* restore the base models to previous version and add the new models separately

* add test for new feature

* adjust the test json for the new feature

* adjust the test json

* modify the conversationItemIndex to optional

* modified the model name

* added cancelAfter in AnalyzeConversationJobRequest

* add version info for the cancelAfter field

* added `cancelAfter` for analyzetext of 2025-05-15-preview

* added examples for AnalyzeConversations and AnalyzeText for 2025-05-15-preview

* removed AnalyzeText for 2025-05-15 and generated it for version 2025-05-15-preview

* modified the readme from 2025-05-15 to 2025-05-15-preview

* fix Typespec validation

* renamed the 'Conversation' to `AIConversation`

* renamed analysisInput and parameters in Request

* remove `role` in ConversationalAIItem

* removed the `ConversationalAIPrediction` class

* modified the `array` to `[ ]`

* changed cancelAfter: float to cancelAfterSeconds: int

* changed `array` to `[ ]` for version 2025-05-15-preview

* restore to 'cancelAfter?: float32;'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
APIStewardshipBoard-SignedOff The Azure API Stewardship team has reviewed and approved the changes. BreakingChange-Approved-Benign Changes are not breaking at the REST API level and have at most minor impact to generated SDKs. Cognitive Services data-plane PublishToCustomers Acknowledgement the changes will be published to Azure customers. TypeSpec Authored with TypeSpec Versioning-Approved-Benign https://github.com/Azure/azure-sdk-tools/issues/6374 VersioningReviewRequired <valid label in PR review process>add this label when versioning review is required
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Cognitive Services Text Analytics API - Azure AI Language] API Review
8 participants