For New Contributors: Update Integration Documentation #15664
Comments
|
🤖 It's great to see your interest in contributing to LangChain! Updating the integration documentation is a valuable contribution that will benefit the entire community. Your efforts will make it easier for users to utilize integrations with the newest LangChain syntax. Thank you for taking on this challenge, and we look forward to seeing your PR. If you have any questions or need assistance, feel free to ask! This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research. Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. If you want to continue the conversation, start your reply with @dosu-bot. |
|
Claiming |
- **Description:**
- Updated the docs for the memory integration module
`aws_dynamodb.ipynb`
- **Issue:**
- #15664
- **Dependencies:**
- N/A
|
Claiming memory/mongodb_chat_message_history.ipynb |
|
@hwchase17 |
|
Claiming |
|
claiming llms/ai21.ipynb |
|
claiming chat/baidu_qianfan_endpoint.ipynb |
- **Description:** Updated the docs for the memory integration module redis_chat_message_history.ipynb - **Issue:** #15664 - **Dependencies:** N/A Co-authored-by: Mu Xianming <mu.xianming@lmwn.com>
we should not use ConversationEntityMemory, and instead update to be more similar to the linked notebook about sql |
…pynb (#15889) - **Description:** Updated Integration Documentation for [llms/ai21.ipynb](https://github.com/langchain-ai/langchain/blob/master/docs/docs/integrations/llms/ai21.ipynb) - **Issue:** #15664, - **Dependencies:** NA, - **Twitter handle:** @Bhadreshsavani
- **Description:** Updated the docs for the chat integration module baidu_qianfan_endpoint.ipynb - **Issue:** #15664 - **Dependencies:**N/A
|
@hwchase17 are they all complete? I don't see the list the OP talks about. |
|
Claiming |
|
Claiming memory/sqlite..ipynb |
|
Related issue #16911 for anyone looking to contribute! |
Description: Updated doc for llm/aleph_alpha with new functions: invoke. Changed structure of the document to match the required one. Issue: #15664 Dependencies: None Twitter handle: None --------- Co-authored-by: Radhakrishnan Iyer <radhakrishnan.iyer@ibm.com>
|
claiming docs/docs/integrations/chat/mistralai.ipynb |
|
Claiming docs/integrations/chat/bedrock |
|
claiming |
…#17014) <!-- Thank you for contributing to LangChain! Please title your PR "<package>: <description>", where <package> is whichever of langchain, community, core, experimental, etc. is being modified. Replace this entire comment with: - **Description:** a description of the change, - **Issue:** the issue # it fixes if applicable, - **Dependencies:** any dependencies required for this change, - **Twitter handle:** we announce bigger features on Twitter. If your PR gets announced, and you'd like a mention, we'll gladly shout you out! Please make sure your PR is passing linting and testing before submitting. Run `make format`, `make lint` and `make test` from the root of the package you've modified to check this locally. See contribution guidelines for more information on how to write/run tests, lint, etc: https://python.langchain.com/docs/contributing/ If you're adding a new integration, please include: 1. a test for the integration, preferably unit tests that do not rely on network access, 2. an example notebook showing its use. It lives in `docs/docs/integrations` directory. If no one reviews your PR within a few days, please @-mention one of @baskaryan, @eyurtsev, @hwchase17. --> - **Description: changes to you.com files** - general cleanup - adds community/utilities/you.py, moving bulk of code from retriever -> utility - removes `snippet` as endpoint - adds `news` as endpoint - adds more tests <s>**Description: update community MAKE file** - adds `integration_tests` - adds `coverage`</s> - **Issue:** the issue # it fixes if applicable, - [For New Contributors: Update Integration Documentation](#15664 (comment)) - **Dependencies:** n/a - **Twitter handle:** @scottnath - **Mastodon handle:** scottnath@mastodon.social --------- Co-authored-by: Bagatur <baskaryan@gmail.com>
|
Claiming docs/integrations/tools/pubmed.ipynb |
- **Description:** Update the docs for the tool integration module `file system` - **Issue:** [For New Contributors: Update Integration Documentation #15664](#15664 (comment)) - **Dependencies:** N/A
Issue you'd like to raise.
Hello LangChain community,
We're always happy to see more folks getting involved in contributing to the LangChain codebase.
This is a good first issue if you want to learn more about how to set up
for development in the LangChain codebase.
Goal
Your contribution will make it easier for users to use integrations with the newest LangChain syntax
Context
As you may have noticed, we’ve recently gone to LangChain 0.1. As part of this, we want to update integration pages to be consistent with new methods. These largely include: (a) new methods for invoking integrations and chains (
invoke,stream), (b) new methods for creating chains (LCEL,create_xyz_..).There are a lot of integrations, so we’d love community help! This is a great way to get started contributing to the library as it will make you familiar with best practices and various integrations.
Set up for development
There are lots of integration notebooks in https://github.com/langchain-ai/langchain/tree/master/docs/docs/integrations. After making changes there, you should run
make formatfrom the root LangChain directory to run our formatter.Shall you accept
Shall you accept this challenge, please claim one (and only one) of the modules from the list
below as one that you will be working on, and respond to this issue.
Once you've made the required code changes, open a PR and link to this issue.
Acceptance Criteria
invoke,stream, etc)Examples
We've gotten started with some examples to show how we imagine these integration pages should look like. The exact format may look different for each type of integration, so make sure to look at the type you are working on:
Your contribution
Please sign up by responding to this issue and including the name of the module.
Suggestion:
No response
The text was updated successfully, but these errors were encountered: