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
In every project we end up creating a custom Button component. We can already do this at the level of our template.
Expected outcome
Button is implemented using the Pressable primitive
Button expects text label and/or icon
We have a disabled state for non active buttons
We handle the press event by changing opacity
We offer two flavours: Primary (a button with clear border outline and a background colour) and Secondary (just text on transparent background, like we have currently "increment counter")
Button accepts a style property to overwrite styles when needed (that allows us to easily create derivative button classes from it)
In every project we end up creating a custom Button component. We can already do this at the level of our template.
Expected outcome
Pressable
primitivedisabled
state for non active buttonsstyle
property to overwrite styles when needed (that allows us to easily create derivative button classes from it)Notes
The text was updated successfully, but these errors were encountered: