clockworklabs / clockworklabs/SpacetimeDB
Prettify migration plan at client
Open
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 pre_publish API generates a prettified migration plan and sends it as bytes over the wire. This is not ideal. Eventually, we only want to send a serialized, semi-structured format of the migration plan and let the client handle pretty-printing.
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 by tracing the pre_publish API and how the client currently receives and renders the migration plan. Define the serialized semi-structured format, update both sides to use it, and verify that the client produces the expected pretty-printed plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100