-
Notifications
You must be signed in to change notification settings - Fork 16k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Add FalkorDB Chat Message History and Update Package Registry #28914
docs: Add FalkorDB Chat Message History and Update Package Registry #28914
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
a2dc382
to
36bc8dc
Compare
c22931a
to
f3d8c52
Compare
Hi @efriis, I created a PR that includes only the requested changes to the I went ahead provided provider pages for them : ) , but Vercel still fails : (. So now I've reverted back to my initial FalkorDB-specific commit. Pls, could you clarify what I need to adjust to move this forward? |
1 similar comment
Hi @efriis, I created a PR that includes only the requested changes to the docs and libs/package.yml files. However, Vercel keeps failing because the following lacked providers pages: exa, prompty, sema4, google-genai, google-vertexai, google-community, nvidia-ai-endpoints, postgres, azure-dynamic-sessions, and sqlserver. I went ahead provided provider pages for them : ) , but Vercel still fails : (. So now I've reverted back to my initial FalkorDB-specific commit. Pls, could you clarify what I need to adjust to move this forward? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's worth updating the vector store page as well to point to the langchain-falkordb
implementation instead of langchain-community
.
"```python\n", | ||
"from langchain_community.vectorstores.falkordb_vector import FalkorDBVector\n", | ||
"```\n", | ||
"or \n", | ||
"\n", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO we should remove the community import. Otherwise readers could be confused about which implementation is recommended.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would love to do that but I'm really scared of opening another PR that will take months to close again.
…angchain-ai#28914) This commit updates the documentation and package registry for the FalkorDB Chat Message History integration. **Changes:** - Added a comprehensive example notebook falkordb_chat_message_history.ipynb demonstrating how to use FalkorDB for session-based chat message storage. - Added a provider notebook for FalkorDB - Updated libs/packages.yml to register FalkorDB as an integration package, following LangChain's new guidelines for community integrations. **Notes:** - This update aligns with LangChain's process for registering new integrations via documentation updates and package registry modifications. - No functional or core package changes were made in this commit. --------- Co-authored-by: Chester Curme <[email protected]>
This commit updates the documentation and package registry for the FalkorDB Chat Message History integration.
Changes:
Added a comprehensive example notebook falkordb_chat_message_history.ipynb demonstrating how to use FalkorDB for session-based chat message storage.
Added a provider notebook for FalkorDB
Updated libs/packages.yml to register FalkorDB as an integration package, following LangChain's new guidelines for community integrations.
Notes:
This update aligns with LangChain's process for registering new integrations via documentation updates and package registry modifications.
No functional or core package changes were made in this commit.