You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While using string content for Banner.Message is the recommended approach for most use cases, there are situations where more complex content might be necessary. For these special cases, Banner.Message now supports ReactNode children.
72
+
While using string content for Banner.Message is the recommended approach for most use cases, there are situations where more complex content might be necessary. For these special cases, Banner support ReactNode as children, so you can nest them directly.
73
73
74
74
<ul>
75
75
<li>Use string content for Banner.Message whenever possible to maintain consistency and proper styling.</li>
76
-
<li>Only use ReactNode when you have specific requirements that cannot be met with string content.</li>
77
-
<li>When using ReactNode content, be mindful of accessibility, responsive behavior, and Equinor design guidelines.</li>
76
+
<li>Only use complex content inside Banner when you have specific requirements that cannot be met with string content.</li>
77
+
<li>When using complex content in Banner, be mindful of accessibility, responsive behavior, and Equinor design guidelines.</li>
78
78
</ul>
79
79
80
-
Some examples where ReactNode might be appropriate:
80
+
Some examples where complex content inside Banner might be appropriate:
81
81
- Content requiring specific formatting (bold text, code elements)
82
82
- Content with structured information that benefits from hierarchical display
0 commit comments