{"version":"2.1.228","anchor":"settings-problems-split-into-notices-and-genuinely-invalid-e","canonical_anchor":"settings-problems-split-into-notices-and-genuinely-invalid-e","heading":"Settings problems split into notices and genuinely invalid entries","tier":"notice","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/settings-problems-split-into-notices-and-genuinely-invalid-e","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Settings problems split into notices and genuinely invalid entries\n\nMinor settings problems now show only in \/status instead of padding the invalid-settings list.\n\n**What**\n\nSettings validation can now mark a problem as informational or as fatal at startup. Informational ones show up in `\/status` but no longer pad out the \"Invalid settings\" list or the invalid-entries dialog; fatal ones are logged at error level.\n\n**Details**\n\n- Validation callbacks flag an issue as status-only or startup-fatal; status-only issues are collected separately as status notices.\n- The invalid-entries dialog and the \"Invalid settings\" list now contain only real validation failures.\n\n**Evidence**\n\n`statusNotices`\n\n- Area: Settings\n- Names: `\/status`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}