clockworklabs / clockworklabs/SpacetimeDB
Rust client SDK: Remove use of `?connection_id` query param to `subscribe` HTTP route
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
Currently, the SDK generates its ConnectionId locally, and passes it to the subscribe HTTP route. This is wrong; the server should (and would, given the opportunity) generate a unique ConnectionId for the connection and return it to the client. Rework the Rust client SDK to that effect.
DoD: When running the Rust client SDK tests, the host logs do not contain any lines like:
2025-02-19T15:53:04.862398Z DEBUG /home/phoebe/clockworklabs/SpacetimeDB/crates/client-api/src/routes/subscribe.rs:74: The connection_id query parameter to the subscribe HTTP endpoint is internal and will be removed in a future version of SpacetimeDB.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the Rust client SDK's subscribe implementation and its Rust client SDK tests; trace how ConnectionId is supplied to the subscribe HTTP route. Verify the completed work by running those tests and confirming the host logs contain no connection_id query-parameter warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100