clockworklabs / clockworklabs/SpacetimeDB

Reimplement: websocket: send/receive reducer & table ids instead of names

Open
#4,789 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

api-break reassessing
Dominant language
Rust
Stars
25.2k
Forks
1.1k
Avg merge
2d 7h
Merged PRs (30d)
46

Description

This issue tracks reimplementation of the work from stale PR #1883, which is being closed because it is too out of date to merge directly.

Original PR: https://github.com/clockworklabs/SpacetimeDB/pull/1883
Original author: @Centril
Original branch: `centril/websocket-use-ids`
Base branch: `master`

## Original PR summary

# Description of Changes

Receive and send reducer ids and table ids as opposed to names in the SDK.

TODO:

Fixes https://github.com/clockworklabs/SpacetimeDBPrivate/issues/1091.

API and ABI breaking changes

Yes.

## Follow-up

- Reimplement this change in a fresh PR against current `master`.
- Carry forward any still-relevant context from the original PR discussion and review.
- Link the new implementation PR back to the original stale PR for historical context.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading stale PR #1883 and its review context, then inspect the current master branch's TypeScript SDK websocket handling. Implement the still-unfinished TypeScript SDK portion so reducer and table IDs are sent and received instead of names, and verify that the API and ABI changes match the already-described host, Rust SDK, and C# SDK behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, rust, typescript
Domain
backend-api-design, databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.