Reassembly context support for tool call response message #463
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…on instead of string
kayhantolga
added
the
Ready for next version
|
I have made some small changes. Please take a look and share your feedback. |
Better revision, good. I've tried to keep the previous naming convention, but that one you've applied is the same i usually use, so better approach, yes. In general, for me, all you have modified is good way to proceed ;) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Refactoring of class "ReassemblyContext" for CreateCompletionAsStream() service API. It replaces the logic about reassembly tool/function calls in mode == "stream" processing to extend and adjust the previous behavior about legacy/deprecated function calls. It allows to get at higher level the same previous reassembled function calls, with the newest API model by tool calls. It works just with ToolCall.Type == "function", but it could be extended in future if new features are introduced following a similar behavior.