[FIX] Update LlamaIndex links

[l145dev]

Description of changes

closes #4446

• Change link for vector store page to point to correct link on LlamaIndex

• Change link of demo Jupyter notebook file to point to correct place in LlamaIndex repository

• Improvements & Bug fixes

  • LlamaIndex link fixes

• New functionality

  • /

Test plan

Open link in a tab and see a non-404 page

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

Migration plan

No

Observability plan

Open the link in a browser

Documentation Changes

No

[propel-code-bot]

Update LlamaIndex Documentation Links

This pull request updates two links in the docs/docs.trychroma.com/markdoc/content/integrations/frameworks/llamaindex.md documentation file. The links for the LlamaIndex vector store page and demo Jupyter notebook have been changed to correct URLs, ensuring users are directed to current, non-404 locations within the official LlamaIndex resources.

Key Changes

• Updated the LlamaIndex vector store page link to https://developers.llamaindex.ai/python/examples/vector_stores/chroma_metadata_filter/
• Updated the demo Jupyter notebook link to reference the correct file location and commit in the LlamaIndex GitHub repository

Affected Areas

• docs/docs.trychroma.com/markdoc/content/integrations/frameworks/llamaindex.md

This summary was automatically generated by @propel-code-bot

[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)