docs(core): add message-type-specific documentation for message name fields
#32469
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
Co-authored-by: Maxime Grenu <[email protected]> Co-authored-by: Claude <[email protected]> Co-authored-by: Claude <[email protected]> Co-authored-by: jmaillefaud <[email protected]> Co-authored-by: Eugene Yurtsev <[email protected]> Co-authored-by: tanwirahmad <[email protected]> Co-authored-by: Christophe Bornet <[email protected]> Co-authored-by: Copilot <[email protected]> Co-authored-by: niceg <[email protected]> Co-authored-by: Chaitanya varma <[email protected]> Co-authored-by: dishaprakash <[email protected]> Co-authored-by: Chester Curme <[email protected]> Co-authored-by: Copilot <[email protected]> Co-authored-by: Kanav Bansal <[email protected]> Co-authored-by: Aleksandr Filippov <[email protected]> Co-authored-by: Alex Feel <[email protected]>
# Conflicts: # .github/workflows/_integration_test.yml # .github/workflows/_release.yml # .github/workflows/api_doc_build.yml # .github/workflows/people.yml # .github/workflows/run_notebooks.yml # .github/workflows/scheduled_test.yml # SECURITY.md # docs/docs/integrations/vectorstores/pgvectorstore.ipynb # libs/langchain_v1/langchain/chat_models/base.py # libs/langchain_v1/tests/integration_tests/chat_models/test_base.py # libs/langchain_v1/tests/unit_tests/chat_models/test_chat_models.py
Co-authored-by: Mason Daugherty <[email protected]> Co-authored-by: Eugene Yurtsev <[email protected]> Co-authored-by: Mason Daugherty <[email protected]> Co-authored-by: Nuno Campos <[email protected]>
Co-authored-by: Kanav Bansal <[email protected]> Co-authored-by: Pranav Bhartiya <[email protected]> Co-authored-by: Nelson Sproul <[email protected]> Co-authored-by: John Bledsoe <[email protected]>
Resolves #32215 --------- Co-authored-by: Chester Curme <[email protected]> Co-authored-by: Eugene Yurtsev <[email protected]> Co-authored-by: Nuno Campos <[email protected]>
Adds backward compat for `.text()` on messages while keeping `.text` access _The kicker:_ Any previous use of `.text()` will now need a `# type: ignore[operator]` to silence type checkers. However, it will still behave as expected at runtime. Deprecating in v0.4.0, to be removed in v2.0.0.
Co-authored-by: Mason Daugherty <[email protected]>
To prevent polluting future PRs
# Conflicts: # libs/core/langchain_core/version.py # libs/core/pyproject.toml # libs/core/uv.lock # libs/partners/openai/tests/integration_tests/chat_models/test_responses_api.py # libs/partners/openai/uv.lock
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
CodSpeed WallTime Performance ReportMerging #32469 will not alter performanceComparing
|
CodSpeed Instrumentation Performance ReportMerging #32469 will not alter performanceComparing Summary
Footnotes |
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.
Updates the name field documentation in v1 messages to provide message-type-specific guidance instead of generic descriptions. The current documentation incorrectly presents the field as purely "human-readable" when it serves critical functional purposes that vary by message type.
ToolMessage.nameis effectively required by most providers despite being typed asOptional[str]AIMessage.nameis critical for multi-agent systems but optional for single-agent scenariosExamples
langchain-openaiAIMessage.namenamewhen present on a messageToolMessage.namelanggraph-supervisor-pyAIMessage.namelangchain-googleFunctionResponseobjectslangchain-communitymessage.namefor tool/function calling