{"version":"2.1.239","anchor":"remote-managed-settings-gain-a-mock-fetcher-and-shared-valid","canonical_anchor":"remote-managed-settings-gain-a-mock-fetcher-and-shared-valid","heading":"Remote managed settings gain a mock fetcher and shared validation","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/remote-managed-settings-gain-a-mock-fetcher-and-shared-valid","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Remote managed settings gain a mock fetcher and shared validation\n\nRemote managed settings can be faked in testing, and payload checking now lives in one place.\n\n**What**\n\nPayload validation and salvage for remote managed settings moved into one shared helper, and a mock fetcher can force a failure, an empty result, or a payload from a JSON file or string.\n\n**Details**\n\n- Mock results carry canned `parse_error` or `unknown_error` outcomes and the checksum `\"mock\"`.\n- Active only when a mock source is configured; otherwise it returns nothing and the real fetch runs.\n\n**Evidence**\n\n`mocked fetch failure`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}