Skip to content

Use WASM Client - #10

Merged
rjb32 merged 2 commits into
mainfrom
refactor/use-wasm-client
Nov 9, 2026
Merged

rjb32 merged 2 commits into
mainfrom
refactor/use-wasm-client

Conversation

@sulaimansuhas

Copy link
Copy Markdown
Contributor

Send queries through the turingdb npm wasm client instead of fetch + JSON, and make the test mocks and server setup speak the protocol.

Send queries through the turingdb npm wasm client (binary protocol, USE_TURING_PROTO=1) instead of fetch + JSON, and make the test mocks and server setup speak the protocol.
@vercel

vercel Bot commented Nov 4, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
turingdb-visualizer Ready Ready Preview Nov 9, 2026 5:37pm UTC
turingdb-visualizer2 Ready Ready Preview Nov 9, 2026 5:37pm UTC

Request Review

Bump the turingdb npm client from 3.0.3-dev to 3.1.0. Its API is
additive (query parameters, Point, PARAMETER_ERROR), so api.ts is
unchanged.

The turingdb 3.1 server speaks the binary protocol by default, so stop
setting USE_TURING_PROTO=1 in the integration setup.

Route the integration setup's readiness probe through TuringClient
instead of a raw fetch, so nothing in the repo calls the server
directly. Mark the fetch + JSON transport in the query panel notes as
superseded and fix a stale comment in setup-fetch.ts.

Verified against pip turingdb 3.1: npm run test:api (27/27), the
Playwright suite (17/17), and the dev and production builds driven in
a browser against a live server.

This branch was successfully deployed

2 active deployments
Preview – turingdb-visualizer — 3a5ecc79 Deployed Nov 9, 2026 by vercel[bot]
Preview – turingdb-visualizer2 — 3a5ecc79 Deployed Nov 9, 2026 by vercel[bot]
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.

2 participants