{"version":"2.1.248","anchor":"config-namespaces-merged-into-one-validated-registry","canonical_anchor":"config-namespaces-merged-into-one-validated-registry","heading":"Config namespaces merged into one validated registry","tier":"internal","area":"Configuration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/config-namespaces-merged-into-one-validated-registry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Config namespaces merged into one validated registry\n\nAll config declarations merged into one registry with range and allowed-value constraints.\n\n**What**\n\nThe 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.\n\n**Evidence**\n\n`C.enum([\"enforce\", \"observe\", \"off\"])`\n\n- Area: Configuration\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}