{"version":"2.1.233","anchor":"frontmatter-errors-now-say-what-actually-happens-at-load-tim","canonical_anchor":"frontmatter-errors-now-say-what-actually-happens-at-load-tim","heading":"Frontmatter errors now say what actually happens at load time","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/frontmatter-errors-now-say-what-actually-happens-at-load-tim","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Frontmatter errors now say what actually happens at load time\n\nBroken frontmatter errors now tell you what will actually happen to that component at load time.\n\n**What**\n\nWhen a component's YAML frontmatter fails to parse, the validator tells you the runtime consequence for that specific component type rather than a generic parse error.\n\n**Details**\n\n- A project agent does not load at all and is treated as a co-located reference document.\n- A plugin agent loads with its name taken from the filename and every other field dropped.\n- Other component types load with empty metadata.\n- A frontmatter block that parses to null is now accepted as an empty mapping instead of reported as a type error.\n\n**Evidence**\n\n`At runtime this agent loads with its name taken from the filename and every other frontmatter field silently dropped.`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}