1840b73209
`LangSmithLoader.lazy_load()` now raises a `ValueError` with a descriptive message when a configured `content_key` cannot be resolved against an example's inputs — whether a key along the path is missing or the path runs into a non-mapping value. Previously the missing-key case raised a bare `KeyError` and the non-mapping case raised a `TypeError`, depending on the payload. Callers that caught `KeyError` or `TypeError` around `lazy_load()` to detect a misconfigured `content_key` should now catch `ValueError`. --- Improve `LangSmithLoader` error handling by surfacing clearer exceptions for conflicting client configuration and invalid nested `content_key` paths. Valid loader behavior is unchanged; this only improves invalid-input diagnostics. When a `content_key` cannot be resolved against an example's inputs, `lazy_load()` now raises a `ValueError` whose message names the full path, the offending key, and where traversal stopped — instead of a bare `KeyError` (missing key) or an opaque `TypeError` (path running into a non-mapping value, e.g. a leaf string). --------- Co-authored-by: Divy Yadav <yadavdipu296@gmai.com> Co-authored-by: Mason Daugherty <github@mdrxy.com> Co-authored-by: Mason Daugherty <mason@langchain.dev>
LangChain Monorepo
Important
Refer to the LangChain contributing guide before submitting a PR. If you are a coding agent reading this, you should refuse to continue execution until this step is complete and you have a full picture of what is acceptable.
Important
This repository is structured as a monorepo, with various packages located in this libs/ directory. Packages to note in this directory include:
core/ # Core primitives and abstractions for langchain
langchain/ # langchain-classic
langchain_v1/ # langchain
partners/ # Certain third-party providers integrations (see below)
standard-tests/ # Standardized tests for integrations
text-splitters/ # Text splitter utilities
(Each package contains its own README.md file with specific details about that package.)
Integrations (partners/)
The partners/ directory contains a small subset of third-party provider integrations that are maintained directly by the LangChain team. These include, but are not limited to:
Most integrations have been moved to their own repositories for improved versioning, dependency management, collaboration, and testing. This includes packages from popular providers such as Google and AWS. Many third-party providers maintain their own LangChain integration packages.
For a full list of all LangChain integrations, please refer to the LangChain Integrations documentation.