Config values now parse through a typed schema that can tell "off" apart from "never set".
What's wrong with this entry?
Several hundred environment and config values are now declared with typed constructors instead of ad-hoc parsing. One of them, a three-state boolean, returns true, false, or nothing at all when the variable is unset, so a setting that is explicitly off can be told apart from one that was never set and should defer to a remote or policy default.
- The other constructors cover strings, integers and enumerations; the string coercion turns text into a boolean, and the enumeration trims the value and rejects anything not on its list.
triBool: () => f(),
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.223
Invalid config dialog is now awaited before returning
Both mention configuration
-
v2.1.228
Env vars set to an empty string now count as unset
Both mention configuration
-
v2.1.228
Config backup moved into a shared helper
Both mention configuration