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
For some components, we created our own primitives AND designed them according to our mockups. In the same time, we have other uses for the primitives.
I think it would be a good idea to create 'unstyled" versions of those components, so they can also be reused for said purposes.
I noticed a few places on other projects where we start from scratch, because we don't have the primitive (without the said styled) exported.
Maybe this first improvement could bring a standard for naming/structuring export of those primitives.
Good candidates so far:
Link: UnstyledLink has that purpose but is only used internally
Button
IconButton (could have same primitive as Button)
The text was updated successfully, but these errors were encountered:
Description
For some components, we created our own primitives AND designed them according to our mockups. In the same time, we have other uses for the primitives.
I think it would be a good idea to create 'unstyled" versions of those components, so they can also be reused for said purposes.
I noticed a few places on other projects where we start from scratch, because we don't have the primitive (without the said styled) exported.
Maybe this first improvement could bring a standard for naming/structuring export of those primitives.
Good candidates so far:
Link
:UnstyledLink
has that purpose but is only used internallyButton
IconButton
(could have same primitive asButton
)The text was updated successfully, but these errors were encountered: