fix: Multimodal type conversion to Converse API format #579
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
michaelnchin
force-pushed
the
converse-mimetype-conversion
branch
from
2e7821f to
12795fa
Compare
3coins
reviewed
Aug 18, 2025
There was a problem hiding this comment.
@michaelnchin
Added some minor suggestions, none of these should be blocker to merge.
…haelnchin/langchain-aws into converse-mimetype-conversion
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.
Fixes #574.
This PR updates the LangChain -> Bedrock message conversion utility in ChatBedrockConverse to correctly convert multimodal input MIME types to Converse API format (where supported).