-
Notifications
You must be signed in to change notification settings - Fork 671
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Text isn't using default variant without passing a variant prop. #1024
Comments
It's because the update to the Text component hasn't landed in a stable release yet. The docs probably shouldn't dictate something that isn't in the default branch. |
Just discovered this as well. Glad I found this issue, since I've been fruitlessly trying to solve this over the last hour. Thanks for posting @pkrawc . Guess I'll resort to putting in |
@cameronwlewis and whomever else finds this until close. You can solve the issue by upgrading your package to |
@pkrawc Thank you so much for the @next tip! |
Description
According to the docs the
<Text/>
component should use thetext.default
variant automatically, when implemented withnext
it does not inherit the default value.Screens
In the bottom section, the card on the left is explicitly declaring
variant: default
and the card next to it isn't. Both are using the<Text/>
component from theme-uiThe text was updated successfully, but these errors were encountered: