Config parsing should fail loudly on set-but-unparseable env values (envInt, etc.) #80
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Extends the fix on PR #78 (#63).
The config env helpers (
envInt, and any peers) silently fall back to the default when an env var is set but unparseable — the same silent-failure pattern @sneak flagged for the duration parser: a set-but-invalid config value should fail loudly and prevent startup, not be silently ignored.Definition of done:
envInt(and any other set-but-unparseable-swallowing helpers) return an error on a set-but-unparseable valueconfig.Newpropagates it so startup aborts on bad configNote: this is an intentional behaviour change — an existing deployment with a malformed config value will now fail to start rather than run with a silently-substituted default.