[DOC]: Update improper usage of $contains operator in example code and add test to validate it

[hesreallyhim]

Description of changes

In various files in the codebase, the string: {$contains: {"text": "hello"}} was used as an example of a where_document query. This is ill-formed for two reasons: (i) $contains does not appear in quotation marks (OK in JS, not in python); (ii) the structure does not conform to the WhereDocument Type: $contains cannot be the key for a value that is a dictionary of two strings. See:

WhereDocumentOperator = Union[
    Literal["$contains"], Literal["$not_contains"], LogicalOperator
]
WhereDocument = Dict[WhereDocumentOperator, Union[str, List["WhereDocument"]]]

in base_types.py

Regrettably, this snippet was referenced in the API docs for langchain-chroma, which is what led me to find and make this fix.

Summarize the changes made by this PR.

• Replace occurrences of {$contains: {"text": "hello"}} with {"$contains": "hello"} in any comments or documentation.
• Add a failing test for {"$contains": {"text": "hello"}}

Test plan

How are these changes tested?

• I added a test (failure) case for the ill-formed {$contains: {"text": "hello"}}. After setting up my basic environment, I was able to run the unit test, and see that it passed. However, I've been struggling to get a full development environment setup, so I have not been able to fully run all the tests.

• Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[hesreallyhim]

strictly speaking, this is not necessary, but it seems to follow the stylistic conventions of the current file, so I made this change

[Copilot]

Pull Request Overview

This PR fixes the incorrect example usage of the "$contains" operator in documentation and code comments and adds a negative unit test to validate that the ill-formed input raises a ValueError.

• Corrects documentation examples in Python, JavaScript, and async API endpoints to use the valid format {"$contains": "hello"} instead of {$contains: {"text": "hello"}}.
• Adds a failing test case in the Python test suite to ensure inappropriate where_document queries are rejected.

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
chromadb/test/test_api.py	Added tests ensuring that improper where_document queries raise a ValueError
clients/js/packages/chromadb-core/src/Collection.ts	Updated documentation comment examples to enclose $contains in quotes
docs/docs.trychroma.com/markdoc/content/reference/js/collection.md	Updated example usage of whereDocument to the correct format
docs/docs.trychroma.com/markdoc/content/reference/python/collection.md	Corrected the example for where_document to show {"$contains": "hello"}
chromadb/api/models/AsyncCollection.py	Adjusted docstring examples for the where_document parameter to the proper format
chromadb/api/models/Collection.py	Made similar updates in docstrings for the where_document parameter

[hesreallyhim]

btw it looks like the workflow keeps failing even after I updated the title to conform to the convention, I'm not sure if it's flakey or I need to do something. Thanks.

[jairad26]

thanks for the PR! Will take a look at the failing title, if it happens again you can push an empty commit and it'll resolve, the header looks fine now

[hesreallyhim]

oh ok yeah i'll try that, i think it said it wouldn't run until there was another commit, but i noticed a few other PR's were hanging, so I wasn't sure if the CI/CD was flakey

[vercel]

Deployment failed with the following error:

The provided GitHub repository does not contain the requested branch or commit reference. Please ensure the repository is not empty.

[hesreallyhim]

@itaismith @jairad26 sorry i'm not sure what the status is regarding the build, I don't want this to just idle here, lmk if you need anything from me.

[hesreallyhim]

oh i think i need approval for the workflow itself to be run:
https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/approving-workflow-runs-from-public-forks#approving-workflow-runs-on-a-pull-request-from-a-public-fork