All config declarations merged into one registry with range and allowed-value constraints.
What's wrong with this entry?
The typed config declarations are collected into a single object rather than scattered namespaces, giving uniform parsing of environment values. Integer entries can now declare minimum, maximum and digits-only constraints, and some entries carry explicit value lists, such as a policy that must be enforce, observe or off.
C.enum(["enforce", "observe", "off"])
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