axodotdev / axodotdev/cargo-dist
do error message pass (especially for generic/js)
- Dominant language
- Rust
- Stars
- 2.1k
- Forks
- 149
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 32
Description
repro
1. add dist-workspace.toml
2. run cargo dist init
```
✔ added [dist] to your root dist-workspace.toml
✔ cargo-dist is setup!
running 'cargo dist generate' to apply any changes
× cargo dist panicked.
├─▶ at cargo-dist/src/build/generic.rs:59:26
╰─▶ A build command is mandatory for generic builds
help: set the `RUST_BACKTRACE=1` environment variable to display a backtrace.
```
Contributor guide
Research direction
Reproduce the failure with dist-workspace.toml, cargo dist init, and cargo dist generate. Start at cargo-dist/src/build/generic.rs:59:26, then trace the generic and JavaScript error paths; done means the error messages no longer surface an avoidable panic and the reported guidance is clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100