⚠ This page is served via a proxy. Original site: https://github.com
This service does not collect credentials or authentication data.
Skip to content

feat: Add new fields to conversation api#1640

Open
javier-aliaga wants to merge 2 commits intodapr:masterfrom
javier-aliaga:update-conversation-api
Open

feat: Add new fields to conversation api#1640
javier-aliaga wants to merge 2 commits intodapr:masterfrom
javier-aliaga:update-conversation-api

Conversation

@javier-aliaga
Copy link
Contributor

Description

Add new fields for conversation api

Issue reference

We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.

Please reference the issue this PR will close: #1639

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

  • Code compiles correctly
  • Created/updated tests
  • Extended the documentation

@javier-aliaga javier-aliaga force-pushed the update-conversation-api branch 2 times, most recently from 3b8b13b to cc22ce8 Compare February 5, 2026 11:31
@javier-aliaga javier-aliaga marked this pull request as ready for review February 5, 2026 11:36
@javier-aliaga javier-aliaga requested review from a team as code owners February 5, 2026 11:36
Signed-off-by: Javier Aliaga <javier@diagrid.io>
@javier-aliaga javier-aliaga force-pushed the update-conversation-api branch from cc22ce8 to c75ca06 Compare February 5, 2026 12:21
@salaboy salaboy self-requested a review February 5, 2026 14:39
@salaboy
Copy link
Collaborator

salaboy commented Feb 5, 2026

/LGTM .. all green so I think we can merge this

salaboy
salaboy previously approved these changes Feb 5, 2026
Copy link
Contributor

@siri-varma siri-varma left a comment

Choose a reason for hiding this comment

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

@javier-aliaga Quick question, should we also update/create the conversation api examples with these new fields ?

@javier-aliaga
Copy link
Contributor Author

@siri-varma the problem is these new fields are only supported by some components but not the echo service.

I modified the examples to print the usage in case the model is present.

Let me work on the ResponseFormat, I would like to do a real test

Signed-off-by: Javier Aliaga <javier@diagrid.io>
@javier-aliaga javier-aliaga force-pushed the update-conversation-api branch from 103cfb2 to 02fa598 Compare February 5, 2026 18:46
@codecov
Copy link

codecov bot commented Feb 5, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.18%. Comparing base (f6c5400) to head (02fa598).

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #1640      +/-   ##
============================================
+ Coverage     78.99%   79.18%   +0.19%     
- Complexity     2096     2122      +26     
============================================
  Files           228      231       +3     
  Lines          6322     6386      +64     
  Branches        693      695       +2     
============================================
+ Hits           4994     5057      +63     
- Misses          976      978       +2     
+ Partials        352      351       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[1.17] Add Conversation API new fields

3 participants