config_opt_wrong_type

Summary

option `{0}` has wrong type: expected {1}, got {2}

Help

set {0} as a {1} literal in [opts]

Details

When this fires

The opts resolver in crates/nanook-core/src/config/opts.rs found the key but the TOML value's variant doesn't match what the caller asked for, and no built-in coercion (string-to-int, int-to-float, string-to-bool) covered the gap. The diagnostic shows the opt key, the expected kind, and what it actually got. Underlined at the offending span in your nanook.toml. Encountered during nanook check and nanook run.

What to check

string list opts want a TOML array; string map opts want an inline table; durations are string literals, not bare numbers. Most failures are quoting mistakes (9090 vs "9090", [a, b] vs "a,b").

# bad
opts = { tags = "a,b" }
# good
opts = { tags = ["a", "b"] }