{"version":"2.1.227","anchor":"settings-can-be-pre-loaded-through-the-v5-storage-backend","canonical_anchor":"settings-can-be-pre-loaded-through-the-v5-storage-backend","heading":"Settings can be pre-loaded through the v5 storage backend","tier":"internal","area":"Storage Backend","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/settings-can-be-pre-loaded-through-the-v5-storage-backend","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Settings can be pre-loaded through the v5 storage backend\n\nSettings can be pre-read through the new storage backend, skipping re-parsing when unchanged.\n\n**What**\n\nA new primer reads `settings.json` through the storage backend whenever settings are invalidated, hashing the bytes so unchanged content is not re-parsed, and seeds the result into the settings store. It only runs when a session has a v5 storage backend configured, so it is inert otherwise.\n\n**Details**\n\n- Files over the size cap, missing files, and backend errors fall back to the ordinary raw-file read, with a log line.\n- After a fixed number of consecutive failures the primer switches itself off for the rest of the process.\n\n**Evidence**\n\n`settingsPrime: user settings seeded`\n\n- Area: Storage Backend\n- Names: `settings.json`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}