[WIP] feat: Add support for Consumer and Supplier function callbacks #1719
Conversation
This file contains hidden or 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
tzolov
force-pushed
the
support_consumer_supplier_function_calling
branch
2 times, most recently
from
4849d92 to
c848577
Compare
tzolov
changed the title
- Add support for Java Consumer and Supplier functional interfaces in function callbacks - Handle void type inputs and outputs in function callbacks - Add test cases for void responses, Consumer callbacks, and Supplier callbacks - Update ModelOptionsUtils to properly handle void type schemas Resolves spring-projects#1718 and spring-projects#1277
…a function This change adds the ability to specify the input type class when defining a function callback for the ChatClient. Previously, the input type had to be inferred, which caused issues with lambda expressions due to type erasure. The following new methods have been added: - ChatClient.ChatClientRequestSpec.function(String, String, Class<I>, Function<I, O>) - ChatClient.ChatClientRequestSpec.function(String, String, Class<I>, BiFunction<I, ToolContext, O>) - ChatClient.ChatClientRequestSpec.function(String, String, Class<I>, Consumer<I>) - ChatClient.Builder.defaultFunction(String, String, Class<I>, Function<I, O>) - ChatClient.Builder.defaultFunction(String, String, Class<I>, BiFunction<I, ToolContext, O>) - ChatClient.Builder.defaultFunction(String, String, Class<I>, Consumer<I>) The deprecated methods without the input type parameter have also been kept for backwards compatibility. This change should make it easier to use the ChatClient API, especially when dealing with lambda expressions.
…andling Improves generic type support in function callbacks and JSON schema generation by: - Moving CustomizedTypeReference to ModelOptionsUtils - Updating BeanOutputConverter to use ParameterizedTypeReference - Modifying function callbacks to support generic type resolution - Adding train scheduler test case to validate generic type handling
tzolov
force-pushed
the
support_consumer_supplier_function_calling
branch
from
c848577 to
c30fda6
Compare
|
Replaced by #1746 |
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.
Depends on #1732
Resolves #1718 , #1277 , #1118, #860