Fix broken links - #682
Conversation
258 to go
There was a problem hiding this comment.
Pull Request Overview
This PR fixes numerous broken internal links across LangChain's documentation by updating outdated paths to match the current documentation structure. The changes primarily address link rot caused by documentation reorganization, ensuring users can properly navigate between related pages and access referenced content.
Key changes include:
- Updating concept links from
/oss/concepts/to appropriate/oss/langchain/or/oss/integrations/paths - Fixing how-to guide references to point to current locations
- Correcting integration and tool documentation cross-references
- Removing some outdated content blocks and references
Reviewed Changes
Copilot reviewed 74 out of 74 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| Various vectorstore, tool, and store integration files | Updated broken links to key-value stores, document loaders, and tool documentation |
| Multiple LLM integration files | Fixed warning messages with outdated concept links and removed deprecated content sections |
| Chat model integration files | Updated feature table links and chaining examples to point to current documentation |
| JavaScript integration files | Aligned link paths with Python counterparts for consistency |
| Document loader files | Fixed references to JSON loaders and removed outdated card entries and images |
| Graph and contributing files | Updated various cross-references to match current structure |
|
Preview ID generated: preview-link2-1759173782-a5d4240 |
| ### Using with text splitters | ||
|
|
||
| Anthropic also lets you specify your own splits using [custom document](https://docs.anthropic.com/en/docs/build-with-claude/citations#custom-content-documents) types. LangChain [text splitters](/oss/concepts/text_splitters/) can be used to generate meaningful splits for this purpose. See the below example, where we split the LangChain.js README (a markdown document) and pass it to Claude as context: | ||
| Anthropic also lets you specify your own splits using [custom document](https://docs.anthropic.com/en/docs/build-with-claude/citations#custom-content-documents) types. LangChain text splitters can be used to generate meaningful splits for this purpose. See the below example, where we split the LangChain.js README (a markdown document) and pass it to Claude as context: |
There was a problem hiding this comment.
we have text splitters: https://docs.langchain.com/oss/python/integrations/splitters
There was a problem hiding this comment.
we dont have it for js
|
Preview ID generated: preview-link2-1759174282-b614d96 |
There was a problem hiding this comment.
Pull Request Overview
Copilot reviewed 87 out of 87 changed files in this pull request and generated 1 comment.
Comments suppressed due to low confidence (2)
src/oss/python/integrations/document_loaders/index.mdx:1
- [nitpick] Multiple Card components are missing the
/>self-closing syntax and use separate closing tags instead. For consistency, all Card components should use the same syntax pattern throughout the file.
---
src/oss/python/integrations/document_loaders/index.mdx:1
- [nitpick] This line appears to be removed from the table but the corresponding Card component for Oxylabs might still exist in the cards section. Verify that both the table entry and card are consistently removed or maintained.
---
| <Card | ||
| title="Abso" | ||
| href="/oss/python/integrations/chat/abso" | ||
| href="/oss/integrations/chat/abso" | ||
| > |
There was a problem hiding this comment.
[nitpick] The massive diff in this file contains 631 identical link updates. Consider using a script or automated tool for such bulk changes to avoid manual errors and make future similar updates more efficient.
|
Preview ID generated: preview-link2-1759176402-bed1000 |
|
Preview ID generated: preview-link2-1759176562-1e88d5d |
## Overview <!-- Brief description of what documentation is being added/updated --> ## Type of change **Type:** [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other] ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [ ] I have read the [contributing guidelines](README.md) - [ ] 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 - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
Overview
Type of change
Type: [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other]
Related issues/PRs
Checklist
docs devsrc/docs.jsonif neededAdditional notes