fix: Update OpenAPIServiceConnector to new ChatMessage #8817
+264
−279
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why:
Update
OpenAPIServiceConnector
to handle newChatMessage
formatOpenAPIServiceConnector
does not support the v2.9.xChatMessage
structure #8774What:
request
method in OpenAPI to handle raw responses more effectively.How can it be used:
The changes affect how
OpenAPIServiceConnector
handles newChatMessage
format involving build intool_calls
property.Example usage:
Where
message
should now containtool_calls
property.How did you test it:
Tests verify new behavior of message processing with checks for valid tool calls. Patched OpenAPI methods are mocked to assess correct invocation and response handling. Integration tests are skipped unless specific API keys are set.
Notes for the reviewer:
Pay special attention to the new patch applied to the
request
method of OpenAPI, specifically concerning raw response handling. Ensure the test coverage is sufficient for edge cases in tool call processing and response verification.