* significant cleanup of API ref -- only listing init functions, also
cleaning up tables of refs to various middlewares
* breaking out middleware page into a middleware section with
* overview
* custom middlewares
* prebuilt middlewares
* custom middleware has consolidated content in python re "decorator vs
class based" syntax
* opted to keep config options bc we don't have great API refs for js
still todo:
* general editing
* I think we really want to focus on the "one liner" intros to each
prebuilt
* determine structure for individual middleware sections (do we like
what's here? maybe we don't need the extended examples?)
* need help w/ structure on the index page -- need more conceptual copy
I think?
* we have a diff HITL page that only uses this middleware, what to do
about consolidation there?
* api refs for js
---------
Co-authored-by: Lauren Hirata Singh <lauren@langchain.dev>
## Overview
Updated `langchain-ibm` and `langchain-db2` docs,
Added correct icons,
Makes `IBM` more visible
## Type of change
**Type:** Update existing documentation
## 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 -->
- [x] I have read the [contributing guidelines](README.md)
- [x] I have tested my changes locally using `docs dev`
- [x] All code examples have been tested and work correctly
- [ ] I have used **root relative** paths for internal links
- [x] 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 -->
---------
Co-authored-by: Mason Daugherty <github@mdrxy.com>
Co-authored-by: Mason Daugherty <mason@langchain.dev>
## Overview
Updated `langchain-ibm` reference documentation
## Type of change
**Type:** [Replace with: New documentation page / Update existing
documentation / Fix typo/bug/link/formatting / Remove outdated content /
Other]
- Update existing documentation: Updated `langchain-ibm` reference
documentation
## 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 -->
- [x] I have read the [contributing guidelines](README.md)
- [x] I have tested my changes locally using `docs dev`
- [x] 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 -->
Added
[langchain-azure-storage](https://pypi.org/project/langchain-azure-storage/)
to the reference docs with a new documentation page. We also plan to
create another PR to update the main LangChain documentation so that it
points to our newly created document loader instead of a previous
implementation. This PR is only to update the reference docs.
## Checklist
<!-- Put an 'x' in all boxes that apply -->
- [x] I have read the [contributing guidelines](README.md)
- [x] I have tested my changes locally using `docs dev`
- [x] All code examples have been tested and work correctly
- [x] 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)
---------
Co-authored-by: Mason Daugherty <github@mdrxy.com>
## Overview
- Added updates for Azure Cosmos DB Vector Store in the for
langchain-azure-ai repo.
## Type of change
**Type:** Update existing documentation / Remove outdated content
---------
Co-authored-by: Mason Daugherty <github@mdrxy.com>
Sydney Runkle