-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
feat: adjust theme structure #3084
Conversation
@@ -82,7 +82,10 @@ const DrawerItem = ({ | |||
: 'transparent'; | |||
const contentColor = active | |||
? colors?.primary |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't be theme.colors
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In cases where properties overlap i skipped the check, since it would be something like theme.isV3 ? theme.colors.primary : theme.colors.primary
. In cases where it does matter, I use the full theme.colors.key
syntax
3de8a10
to
46f6e35
Compare
The mobile version of example app from this branch is ready! You can see it here |
Summary
After internal discussion, we decided to simplify our approach and make the new theme closer to the old theme in terms of structure. This PR delivers that, plus it has all the necessary
theme.isV3 checks
in componentsTest plan
Run the project locally:
yarn example start