Skip to content

Unconditionally use ts_rs and remove 'ts-bindings' feature#7245

Open
Aaron1011 wants to merge 2 commits intomainfrom
aaron/unconditional-ts-rs
Open

Unconditionally use ts_rs and remove 'ts-bindings' feature#7245
Aaron1011 wants to merge 2 commits intomainfrom
aaron/unconditional-ts-rs

Conversation

@Aaron1011
Copy link
Copy Markdown
Member

@Aaron1011 Aaron1011 commented Apr 8, 2026

The upcoming ts-executor-pool crate will need to access the generated bindings (to show to the LLM when typescript tool calls are enabled).


Note

Medium Risk
Medium risk because it touches Cargo feature/dependency wiring across many crates and changes TypeScript export attributes, which could break builds or generated bindings if any crate relied on the old ts-bindings gating.

Overview
Makes TypeScript bindings generation unconditional by removing the ts-bindings feature flag across the workspace and switching all #[cfg_attr(feature = "ts-bindings", ...)] usages to always-on ts_rs derives/#[ts(...)] attributes.

Updates crate dependencies to include ts-rs/tensorzero-ts-types non-optionally, strips ts-bindings feature definitions from multiple Cargo.tomls, and adjusts the tsbuild cargo alias to no longer pass --features ts-bindings.

Reviewed by Cursor Bugbot for commit 85bda0d. Bugbot is set up for automated code reviews on this repo. Configure here.

The upcoming ts-executor-pool crate will need to access the generated
bindings (to show to the LLM when typescript tool calls are enabled).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants