feat(config): warn on unknown config keys in foundry.toml #10621
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Right now, if a user makes a typo or adds a deprecated field in their local
foundry.toml
, Figment/Serde simply ignores it and the user never knows something went unused. That can lead to confusion or misconfiguration.Solution
Before Figment does
.extract()
into theConfig
struct, we readfoundry.toml
as raw TOML, run it through [serde_ignored
] to collect any unused/unknown keys, and if any are found we log awarn!
listing them. This is non-breaking (we still load all the valid settings) and only affects root keys for now.About #10550 . For now, could I have some feedback on the implementation?
PR Checklist