oxidecomputer / oxidecomputer/crucible
`notify-nexus` could be configurable at runtime instead of through a feature flag
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
Currently notify-nexus is a feature flag that is makes this behaviour choice compile time, not run time. This could be plumbed in CrucibleOpts as a run time option instead, removing the need for the notify-nexus feature flag.
Contributor guide
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 locating the notify-nexus feature flag and CrucibleOpts, then trace where the flag controls behavior. Done means the behavior choice is supplied through a runtime CrucibleOpts option and the compile-time notify-nexus feature flag is no longer needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100