hoist config loading up higher so config can be recycled
- Dominant language
- Rust
- Stars
- 543
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
When you run `oranda dev` we load the config 1+2n times:
* once for dev
* in a loop
* once for build
* once for serve
If loading config was a thing done before "doing" a command, we could more properly load the config once and have the steps take it as an arg.
Ideally the config would be loaded only n times
* once for dev
* in a loop (skipping the first iteration)
* once for build + serve
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the `oranda dev` entry point and trace how config loading is repeated across the build and serve loop. Run `oranda dev` to observe the current load pattern, then verify that the config is loaded at the intended points and reused by build and serve.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100