Skip to content

[ENH] Regenerate JS client library from Chroma 1.0.0 openapi spec - @chromadb and @chromadb-client v2.1.0#3967

Merged
philipithomas merged 11 commits intomainfrom
philipithomas/regenerate-js-client
Mar 25, 2025
Merged

[ENH] Regenerate JS client library from Chroma 1.0.0 openapi spec - @chromadb and @chromadb-client v2.1.0#3967
philipithomas merged 11 commits intomainfrom
philipithomas/regenerate-js-client

Conversation

@philipithomas
Copy link
Member

@philipithomas philipithomas commented Mar 12, 2025

The JS client library leverage the Chroma OpenAPI spec to code-generate bindings.

This PR updates:

  • The code-generation script to be at the latest version
  • Regenerates API code using the Chroma 1.0.0 spec (Rust server)
  • Bumps the JS client libraries to v2.1.0

Related: #3901

@github-actions
Copy link

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)

@philipithomas philipithomas force-pushed the philipithomas/regenerate-js-client branch from 02d00a0 to 954b33a Compare March 17, 2025 15:51
@philipithomas
Copy link
Member Author

Blocked on #4003

@philipithomas philipithomas force-pushed the philipithomas/regenerate-js-client branch from 954b33a to 46e87a1 Compare March 19, 2025 16:57
@philipithomas philipithomas force-pushed the philipithomas/regenerate-js-client branch from 46e87a1 to 3042554 Compare March 25, 2025 17:29
@philipithomas philipithomas changed the title [ENH] regenerate JS client library from 1.0.0 openapi spec [ENH] Regenerate JS client library from Chroma 1.0.0 openapi spec - @chromadb and @chromadb-client v2.1.0 Mar 25, 2025
@philipithomas philipithomas marked this pull request as ready for review March 25, 2025 18:11
@philipithomas philipithomas merged commit 1bb62b6 into main Mar 25, 2025
12 checks passed
Inventrohyder pushed a commit to Inventrohyder/chroma that referenced this pull request Aug 5, 2025
…chromadb and @chromadb-client v2.1.0 (chroma-core#3967)

The JS client library leverage the [Chroma OpenAPI
spec](https://api.trychroma.com:8000/docs/) to code-generate bindings.

This PR updates:

- The code-generation script to be at the latest version 
- Regenerates API code using the Chroma 1.0.0 spec (Rust server)
- Bumps the JS client libraries to v2.1.0

Related: chroma-core#3901
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments