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
Is your feature request related to a problem? Please describe.
Inside of the ExpansionPanel component there is the ability to render text and secondary text elements. Each element is currently hard coded as semantic HTML as span tags. It would be nice to simply render the respective Typography component and pass in the local attributes it cares about.
Describe the solution you'd like
I'd like to either A) rebuild the typography component into multiple ones (H1, H2, H3, Span, etc) to support semantic HTML components or B) rebuild the typography component in the interim to render <span> tags instead of <div> elements.
Describe alternatives you've considered
I have simply just modified the ExpansionPanel markup to support the attributes I care about
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Inside of the
ExpansionPanel
component there is the ability to render text and secondary text elements. Each element is currently hard coded as semantic HTML asspan
tags. It would be nice to simply render the respectiveTypography
component and pass in the local attributes it cares about.Describe the solution you'd like
I'd like to either A) rebuild the typography component into multiple ones (H1, H2, H3, Span, etc) to support semantic HTML components or B) rebuild the typography component in the interim to render
<span>
tags instead of<div>
elements.Describe alternatives you've considered
I have simply just modified the
ExpansionPanel
markup to support the attributes I care aboutAdditional context
N/A
The text was updated successfully, but these errors were encountered: