-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
much improved doc strings for client #290
Conversation
The newly created collection | ||
|
||
Raises: | ||
ValueError: If the collection already exists and get_or_create is False |
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.
Isn't there also some error if the collection doesn't follow naming guidelines?
The collection | ||
|
||
Examples: | ||
>>> client.get_or_create_collection("my_collection") |
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.
This is awesome.
None | ||
|
||
Raises: | ||
ValueError: If you don't provide either embeddings or documents |
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.
There are a bunch of validation errors that could also be thrown? Do we want to surface those here?
chromadb/api/models/Collection.py
Outdated
GetResult: A GetResult object containing the results. | ||
|
||
Raises: | ||
ValueError: If you provide both ids and a where filter |
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.
Do we really do this? I think we support both.
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.
Thanks for doing this. It looks good minus the validaty of the errors I wasn't sure about. Also, can we decide if we want to surface other errors? I'm pretty sure there are errors in validation that we aren't surfacing in the docstrings.
Improved docstrings for chroma-core/docs#28