clockworklabs / clockworklabs/SpacetimeDB
Implement `pre-publish` ONLY in CLI for checking e.g. in CI
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
Either spacetime publish should have a --check or --dry-run flag, or a spacetime pre-publish (or validate) subcommand should exist, acting similarly to publish in terms of /pre-publish but without actually calling the /publish endpoint.
This will be useful for CI purposes, allowing for changes validation (e.g. missing #[default]s).
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 CLI implementation of spacetime publish and how it calls /pre-publish before /publish. Define the chosen --check, --dry-run, or validation-subcommand behavior, then verify that CI can run the pre-publish checks without calling /publish, including validation such as missing #[default]s.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100