{"version":"2.1.289","anchor":"border-style-validation-and-syntax-highlight-fallback","canonical_anchor":"border-style-validation-and-syntax-highlight-fallback","heading":"Invalid Box borderStyle values are now checked and drawn with no border","tier":"notice","area":"Terminal UI","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289\/e\/border-style-validation-and-syntax-highlight-fallback","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289","markdown":"### Invalid Box borderStyle values are now checked and drawn with no border\n\nPlugin UI boxes with an unknown `borderStyle` now get a diagnostic and no border, and diff highlighting stops retrying after an error\n\n**What**\n\nPlugins can draw boxes on screen and give them a `borderStyle`. Claude Code now checks that style.\n\n- Validation: plugin UI trees are checked for an invalid `Box` `borderStyle`. A bad style is removed and a diagnostic message is shown, and the box is drawn with no border.\n\n- Known styles only: the border renderer now accepts only known style names, and a style must supply all eight corner and edge pieces. Before, any style that was set counted as a one-cell border, and an unknown name fell back to a default.\n\n- Validator order: some props now skip the standard per-prop check, while the `borderStyle` accounting still applies.\n\n- Syntax highlighting: when highlighting code in a diff (a view of what changed in a file) throws an error, the language is cleared so it does not keep retrying.\n\n**Why**\n\nA mistyped border style or a highlighting error should no longer break how things are drawn. Plugin authors get a clear message instead of a broken border.\n\n- Area: Terminal UI\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}