core: introduce API to encode return values as response objects #88
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.
We introduce several encoders that can be used to encode any return value to a relevant response type.
Specifically, there is
ToolResponseEncoder
that could be used to encode any return value to aToolResponse
;ContentEncoder
to encode any return value toContent
;ResourceContentsEncoder
toResourceContents
andPromptResponseEncoder
toPromptResponse
.We also register
JsonTextContentEncoder
andJsonTextResourceContentsEncoder
by default. As a result, any "custom" return value returned from a@Tool
method is encoded asTextContent
containing the value encoded as JSON (using Jackson), and any "custom" return value returned from a@Resource
method is encoded asTextResourceContents
containing the value encoded as JSON (using Jackson).