-
-
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: replace old variable references #3062
Conversation
The mobile version of example app from this branch is ready! You can see it here |
0ee879d
to
d3d2bb5
Compare
The mobile version of example app from this branch is ready! You can see it here |
@@ -117,10 +115,10 @@ const AnimatedFABExample = () => { | |||
keyExtractor={_keyExtractor} | |||
onEndReachedThreshold={0} | |||
scrollEventThrottle={16} | |||
style={[styles.flex, { backgroundColor: background }]} | |||
style={[styles.flex, { backgroundColor: colors?.background || '#000' }]} |
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.
As we discussed internally, fallback colors are temporary to not block the PR. All the cases will be refactored in the way: isV3 ? appropriate color from V3 : appropriate color from V2
The mobile version of example app from this branch is ready! You can see it here |
Summary
These changes fix other parts of application when theme V3 would be used instead of V2. Changes:
colors.background
, were replaced with optional chaining or dirty defaults (to be resolved later on, during the works on individual components)