clockworklabs / clockworklabs/SpacetimeDB
C#/Unity SDK - Figure out if server-side updates are already grouped by table
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
Here
and in other places we could simplify quite a bit of code if we can assume that database updates / transaction updates already have updates grouped and deduplicated by table, but it's currently not clear if it's something we can rely on.
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 with src/SpacetimeDBClient.cs around lines 476-478, then trace the server-side database and transaction update behavior. Determine whether updates are guaranteed to be grouped and deduplicated by table, and record the conclusion clearly enough to guide any later simplification of the SDK code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, rust, unity
- Domain
- backend, databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100