{"version":"2.1.227","anchor":"reads-of-the-old-local-settings-file-are-now-reported","canonical_anchor":"reads-of-the-old-local-settings-file-are-now-reported","heading":"Reads of the old local settings file are now reported","tier":"internal","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/reads-of-the-old-local-settings-file-are-now-reported","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Reads of the old local settings file are now reported\n\nReads of the old local settings file are now reported to the caller.\n\n**What**\n\nThe settings loader can notify a caller when it reads a legacy local settings file, distinguishing a read during the full merge of all settings sources from a read of that one source alone.\n\n**Details**\n\n- The callback `onLegacyLocalSettingsRead` receives `\"cascade\"` or `\"per_source\"`; the CLI forwards it to an event emitter.\n\n**Evidence**\n\n`onLegacyLocalSettingsRead`\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}