{"version":"2.1.94","anchor":"settings-parse-and-validation-error-reporting","canonical_anchor":"settings-parse-and-validation-error-reporting","heading":"Settings Parse and Validation Error Reporting","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.94\/e\/settings-parse-and-validation-error-reporting","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.94","markdown":"### Settings Parse and Validation Error Reporting\n\n**What**\n\nSettings files that fail to parse or validate are now reported with structured error information instead of being silently skipped.\n\n**Details**\n\n- New structured error fields: `path` (dot-notation to field), `message` (human-readable), `severity` (set to `\"warning\"`)\n- Settings errors section: \"Settings parse and validation errors. When non-empty, the listed files were skipped during the merge above \u2014 their settings are not reflected in `effective` or `sources`.\"\n- Error types include invalid JSON, JSON comments, and schema mismatches\n- File path of the failing settings file is included in error output\n\n**Evidence**\n\nSettings validation (search for `\"Settings parse and validation errors\"`, `\"severity\"`)"}