fix(ui): avoid component-tag syntax in a Typography comment

check-component-imports scans sources for <Component> tags and requires each to
be imported. The explanatory comment added with the prose-scoping fix wrote
<Blockquote> 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 <noreply@anthropic.com>
This commit is contained in:
2026-08-13 16:58:52 +05:30
co-authored by Claude Opus 5
parent 8393a953b7
commit 2e1b667285
+1 -1
View File
@@ -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
<Blockquote> 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; }