config_opt_invalid

Summary

option `{0}` has invalid value `{1}`: {2}

Help

expected a {3} value

Details

When this fires

The opts resolver in crates/nanook-core/src/config/opts.rs got a value of the right TOML type but couldn't accept it. Examples: an int opt holding a string like "not-a-number", a bool opt with "maybe", a duration opt that fails the duration parser, or a string opt using the @file:<path> include where the file can't be read. The diagnostic names the opt key, shows the raw value, and explains what was expected. Surfaces during nanook check and nanook run when registry validators or builders call into the resolver.

What to check

For @file: includes, confirm the path is readable. For bool opts, accepted forms are true/false/yes/no/on/off/0/1.

# bad
opts = { port = "nope" }
# good
opts = { port = 9090 }