Skip to content

docs: fix ChatGoogleGenerativeAI example to use model instead of modelName - #2150

Merged
Lauren Hirata Singh (lnhsingh) merged 1 commit into
langchain-ai:mainfrom
time1043:patch-1
Jan 22, 2026
Merged

docs: fix ChatGoogleGenerativeAI example to use model instead of modelName#2150
Lauren Hirata Singh (lnhsingh) merged 1 commit into
langchain-ai:mainfrom
time1043:patch-1

Conversation

@time1043

@time1043 time1043 commented Jan 9, 2026

Copy link
Copy Markdown

Overview

This PR fixes an incorrect property name in the ChatGoogleGenerativeAI documentation.
The example currently uses modelName, but the actual constructor and TypeScript types only support the model property.

Type of change

Type: Fix typo/bug/link/formatting

Related issues/PRs

  • GitHub issue: None
  • Feature PR: None
  • Linear issue:
  • Slack thread:

Checklist

  • I have read the contributing guidelines
  • I have tested my changes locally using docs dev
  • All code examples have been tested and work correctly
  • I have used root relative paths for internal links
  • I have updated navigation in src/docs.json if needed

(Internal team members only / optional): Create a preview deployment as necessary using the Create Preview Branch workflow

Additional notes

https://docs.langchain.com/oss/javascript/integrations/chat#google-gemini

image

In the latest version of @langchain/google-genai (^2.1.6), ChatGoogleGenerativeAI expects a model property. The modelName field does not exist in the current implementation.

image image

@github-actions github-actions Bot added javascript external User is not a member of langchain-ai langchain For docs changes to LangChain oss labels Jan 9, 2026
@lnhsingh
Lauren Hirata Singh (lnhsingh) merged commit 0c90190 into langchain-ai:main Jan 22, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

external User is not a member of langchain-ai javascript langchain For docs changes to LangChain oss

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants