Skip to content
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

feat: Improved ChromaDB docs and tests #766

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

tazarov
Copy link

@tazarov tazarov commented May 8, 2024

  • Added additional examples of how to use Chroma
  • Updated documentation with relevant project links
  • Version bumps wherever possible to ensure the default user experience is up to date

Copy link

netlify bot commented May 8, 2024

Deploy Preview for testcontainers-node ready!

Name Link
🔨 Latest commit 7389d97
🔍 Latest deploy log https://app.netlify.com/sites/testcontainers-node/deploys/66b4bb8ae373df00080b7808
😎 Deploy Preview https://deploy-preview-766--testcontainers-node.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@cristianrgreco
Copy link
Collaborator

Hi @tazarov, thanks for raising. The smoke test is failing because the lock file doesn't match the updated dependency. There's also some lint issues.

@cristianrgreco cristianrgreco added maintenance Improvements that do not change functionality patch Backward compatible bug fix labels Jun 15, 2024
@tazarov
Copy link
Author

tazarov commented Aug 6, 2024

@cristianrgreco, thanks for pinging me on this. I'll rebase and fix this tomorrow.

- Added examples for connect, create collection, using embedding functions, auth and persistent dirs
@tazarov tazarov force-pushed the feat/chromadb-improved-docs branch from 7919939 to 14a5b45 Compare August 8, 2024 10:28
@tazarov
Copy link
Author

tazarov commented Aug 8, 2024

@cristianrgreco, rebased from latest main.

@cristianrgreco
Copy link
Collaborator

@tazarov This PR doesn't allow edits from maintainers so I can't fix it myself. Could you merge main? Should be enough to re-run npm install after merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Improvements that do not change functionality patch Backward compatible bug fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants