bootstrap: add debugging aid to identify the *resolved* config value
Open
Nobody has claimed this yet.
C-enhancement
T-bootstrap
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
I wish we had added a command to bootstrap for debugging the resolved value of each config, not just the ones that have been explicitly overridden.
Originally posted by @jyn514 in #136701
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 inspecting bootstrap's existing configuration-reporting command or entry point, especially the path that shows explicitly overridden values. Determine how resolved configuration values are assembled, then define the new debugging output so it reports each resolved value; done means the command exposes those values and has coverage for the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100