{"version":"2.1.229","anchor":"render-errors-are-now-reported-instead-of-silently-blanking","canonical_anchor":"render-errors-are-now-reported-instead-of-silently-blanking","heading":"Render errors are now reported instead of silently blanking","tier":"notice","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/render-errors-are-now-reported-instead-of-silently-blanking","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Render errors are now reported instead of silently blanking\n\nA crash in the interface now reports itself instead of leaving a blank screen.\n\n**What**\n\nThe component that catches crashes in the UI previously just recorded that an error happened and rendered nothing. It now reports the error and calls an optional `onError` handler, so a failed render surfaces rather than disappearing.\n\n**Evidence**\n\n`componentDidCatch`\n\n- Area: Terminal UI\n- Names: `onError`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}