{"version":"2.1.229","anchor":"flag-settings-file-content-is-pinned-and-re-read","canonical_anchor":"flag-settings-file-content-is-pinned-and-re-read","heading":"Flag settings file content is pinned and re-read","tier":"internal","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/flag-settings-file-content-is-pinned-and-re-read","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Flag settings file content is pinned and re-read\n\nFeature-flag settings files are re-read against a pinned expected content instead of trusting one visit.\n\n**What**\n\nThe startup settings context now resolves the expected contents of the flag settings file from a pinned value with a fallback, and new accessors read and replace that pinned value. The settings loader re-reads the flag settings file even when its path was already visited, if expected content is present.\n\n**Evidence**\n\n`flagSettingsFilePinnedContent`\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}