Update manage-collections.md #5383
Conversation
Missing {% TabbedCodeBlock %} and {% Tab label="python" %}
Reviewer ChecklistPlease leverage this checklist to ensure your code review is thorough before approving Testing, Bugs, Errors, Logs, Documentation
System Compatibility
Quality
|
|
This PR updates the documentation file manage-collections.md by inserting the missing Markdoc tab components for a Python code snippet. Specifically, it wraps a previously untagged Python code sample with {% TabbedCodeBlock %} and {% Tab label="python" %} tags. These changes improve documentation structure and code sample clarity but do not alter any product functionality. This summary was automatically generated by @propel-code-bot |
![propel-code-bot[bot]](https://avatars.githubusercontent.com/in/1179004?s=60&v=4){kind=small}
| @@ -82,6 +82,9 @@ collection = client.create_collection( | |||
|
|
|||
| Instead of having Chroma embed documents, you can also provide embeddings directly when [adding data](./add-data) to a collection. In this case, your collection will not have an embedding function set, and you will be responsible for providing embeddings directly when adding data and querying. | |||
|
|
|||
There was a problem hiding this comment.
[Documentation]
The TabbedCodeBlock and Tab tags are opened but never closed. Add {% /Tab %} and {% /TabbedCodeBlock %} after the code block to prevent malformed Markdown/Markdoc rendering.
|
Hi 👋 Thanks for contributing! I think your change breaks the website. Did you get it working on your machine? I think the second codeblock you tried to fix actually shouldn't be there. If you'd like you could remove it! |
Missing {% TabbedCodeBlock %} and {% Tab label="python" %}
Description of changes
Summarize the changes made by this PR.
Test plan
How are these changes tested?
pytestfor python,yarn testfor js,cargo testfor rustMigration plan
Are there any migrations, or any forwards/backwards compatibility changes needed in order to make sure this change deploys reliably?
Observability plan
What is the plan to instrument and monitor this change?
Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs section?