From 2e1b6672853b82979b19747501cc6f9b260ebcb9 Mon Sep 17 00:00:00 2001 From: Ajay Ghanwat Date: Thu, 13 Aug 2026 16:58:52 +0530 Subject: [PATCH] fix(ui): avoid component-tag syntax in a Typography comment check-component-imports scans sources for tags and requires each to be imported. The explanatory comment added with the prose-scoping fix wrote
literally, so the checker demanded an import for a component the file never renders. Naming it without angle brackets keeps the explanation and clears the gate. Co-Authored-By: Claude Opus 5 --- packages/ui/components/Typography.wrn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/ui/components/Typography.wrn b/packages/ui/components/Typography.wrn index a94134a3..18dd2c3e 100644 --- a/packages/ui/components/Typography.wrn +++ b/packages/ui/components/Typography.wrn @@ -90,7 +90,7 @@ component Typography { /* Prose styles apply to raw markup only. Every nested UI component renders inside a `.wrn-component` wrapper, so excluding that subtree stops these element rules from doubling up on a component's own styling — a nested -
otherwise drew two left borders, its own plus this one. + Blockquote otherwise drew two left borders, its own plus this one. The exclusion lives inside :where() so specificity stays at zero and an application can still override any of these with a plain class. */ .wrn-typography :where(h1):not(:where(.wrn-typography .wrn-component *)) { font-size: clamp(2rem, 4vw, 3.5rem); margin: 0 0 1.5rem; }