{"version":"2.1.260","anchor":"legacy-string-encoded-keyvalue-config-values-now-get-a-depr","canonical_anchor":"legacy-string-encoded-keyvalue-config-values-now-get-a-depr","heading":"Legacy string-encoded key\/value config values now get a deprecation notice","tier":"internal","area":"Admin Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/legacy-string-encoded-keyvalue-config-values-now-get-a-depr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Legacy string-encoded key\/value config values now get a deprecation notice\n\nLegacy string-encoded config values now get flagged for scheduled deprecation.\n\nA new `legacyKvEncodingNotice` helper flags managed-config fields that still accept the old `\"Name=value,\u2026\"` string or `[\"Name: value\", \u2026]` array encodings instead of a JSON object, tagging them for a scheduled deprecation batch.\n\n- Area: Admin Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}