{"version":"2.1.259","anchor":"config-parse-error-tracking-becomes-tri-state","canonical_anchor":"config-parse-error-tracking-becomes-tri-state","heading":"Config parse-error tracking becomes tri-state","tier":"internal","area":"Configuration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/config-parse-error-tracking-becomes-tri-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### Config parse-error tracking becomes tri-state\n\nConfig load outcome is now recorded as parsed, parse-error or missing rather than a single parse-error boolean.\n\nThe prior boolean `setLastGetConfigWasParseError` is replaced by `setLastGetConfigOutcome`, which records one of `'parse-error'`, `'enoent'`, or `'parsed'`, giving more granular diagnostics on config load outcomes.\n\n- Area: Configuration\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}