docs: add mime_type to JavaScript PDF file content examples #2007
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
github-actions
bot
added
langchain
chunghyunleeme
force-pushed
the
fix/add-mime-type-to-file-content-examples
branch
from
06e8107 to
d67777d
Compare
Add explicit mime_type: "application/pdf" to JavaScript PDF document input examples (URL and base64) in the messages documentation. This clarifies that mime_type is required when using type: "file" content blocks with url or base64 sources, since providers don't infer MIME type from these sources. Note: file ID examples don't need mime_type since providers already know the MIME type from when the file was uploaded. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
chunghyunleeme
force-pushed
the
fix/add-mime-type-to-file-content-examples
branch
from
d67777d to
8d23727
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
mime_type: "application/pdf"to JavaScript PDF document input examples in the messages documentationIssue
When using
type: "file"content blocks withsource_type: "url"for PDF files, providers like Google Vertex AI require an explicitmime_typefield. However, the current documentation examples don't include this field, which can lead to errors when users follow the examples.For example, without
mime_type, Vertex AI receivesapplication/octet-streamas the default MIME type, which it doesn't recognize as a valid PDF document.Changes
Updated JavaScript examples in
src/oss/langchain/messages.mdx:mime_type: "application/pdf"to URL source examplemime_type: "application/pdf"to base64 source exampleTest plan
🤖 Generated with Claude Code