You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please update the markdown cell in the Jupyter notebook to use the correct URL for the VectorStoreRetriever class. The markdown should be modified as follows:
This creates a retriever (specifically a [VectorStoreRetriever](https://python.langchain.com/api_reference/core/vectorstores/langchain_core.vectorstores.base.VectorStoreRetriever.html)), which we can use in the usual way:
The text was updated successfully, but these errors were encountered:
dosubotbot
added
the
🤖:docs
Changes to documentation and examples, like .md, .rst, .ipynb files. Changes to the docs/ folder
label
Oct 8, 2024
PPraneesh
changed the title
DOC: Incorrect anchor tag URL for VectorStoreRetriever in Vector Store Retriever documentation
DOC: Incorrect API Reference Link in /docs/how_to/vectorstore_retriever/
Oct 8, 2024
URL
https://python.langchain.com/docs/how_to/vectorstore_retriever/
Checklist
Issue with current documentation:
There is an incorrect URL in the anchor tag for the VectorStoreRetriever class in the "How to use a vectorstore as a retriever" documentation page.
Location of the Issue :
The problematic link can be found in this section of the documentation:
https://python.langchain.com/docs/how_to/vectorstore_retriever/#:~:text=VectorStoreRetriever
Current (Incorrect) URL:
https://python.langchain.com/api_reference/core/vectorstores/langchain_core.vectorstores.VectorStoreRetriever.html
Correct URL:
https://python.langchain.com/api_reference/core/vectorstores/langchain_core.vectorstores.base.VectorStoreRetriever.html
The correct URL includes .base in the path, which is missing in the current documentation.
Idea or request for content:
Please update the markdown cell in the Jupyter notebook to use the correct URL for the VectorStoreRetriever class. The markdown should be modified as follows:
The text was updated successfully, but these errors were encountered: