Normalize key messages for all providers
#170
Merged
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
Right now there are some providers, e.g. anthropic that can provide
the content of the messages as a list
```
content: [{'type': 'text', 'text': 'hello?'}]
```
This PR standarizes the content of all messages to string
```
content: 'hello?'
```
The list type was making the DB storage to fail
aponcedeleonch
force-pushed
the
normalize-anthropic
branch
from
3011dda to
6c3b13c
Compare
jhrozek
approved these changes
Dec 3, 2024
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.
Right now there are some providers, e.g. anthropic that can provide the content of the messages as a list
This PR standarizes the content of all messages to string
The list type was making the DB storage to fail