-
Notifications
You must be signed in to change notification settings - Fork 0
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
Expo image #4
Expo image #4
Conversation
af156f6
to
ba026f7
Compare
src/components/Icon/BankIcons.ts
Outdated
}; | ||
|
||
type AssetIcon = { | ||
icon: React.FC<SvgProps>; |
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.
We're using type from react-native-svg
even though we're not really using react-native-svg
here, am I right?
If so, let's try to find some other type here.
src/components/Icon/index.native.js
Outdated
contentFit: PropTypes.string, | ||
|
||
/** Is icon displayed in its own color */ | ||
displayInDefaultIconColor: PropTypes.bool, |
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.
It is confusing for me, that there is a prop available in native only. I'd honestly remove it and make behavior identical to what happens on web - make fill color from theme as default and override it with whatever passed as fill prop, if passed.
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.
But If I want to override it I have to pass null value through the fill property. Is it ok? I've added this property to make code more readable. When we want to display icon in original color, component should not have defined tintColor property or this property's value must be null. Instead of passing null through the fill property I created this prop.
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.
Is there any place where we want to display Icon's color defined in SVG file without any tinting (either with color from theme or passed as property)? If so, why does it work on web without this additional boolean? If no, I think that passing undefined
as fill
is fine
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.
Fill prop behaviour is different when we use expo-image because in this case we set tintColor for whole image, null value allows to use original icon color. When we pass this prop to component transformed by svg-transformer we can set fill prop's value directly in svg asset, it doesn't set this color for whole icon but only for the part which should be displayed in this color. It can be noticed on logo asset which i modified in this PR. I set fill prop's value directly in svg asset and it changed only the logo part of this asset not whole image, small icon which shows environment didn't change
src/components/Icon/index.native.js
Outdated
name: PropTypes.string, | ||
|
||
/** Determines how the image should be resized to fit its container */ | ||
contentFit: PropTypes.string, |
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.
Why is that necessary on native and not on web?
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.
On web we still use @svgr/webpack to transform svg icons to components, icons displayed as a components don't need to be additionally styled
src/components/Icon/index.native.js
Outdated
style={[StyleUtils.getWidthAndHeightStyle(width, height), styles.bgTransparent, styles.overflowVisible]} | ||
> | ||
<View style={iconStyles}> | ||
<Image |
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.
It seems that we could extract this component (and IconComponent
in index.js) to two seperate files (one with native.js
extension) and keep divergence between platforms at its minimum.
@@ -44,7 +45,7 @@ const propTypes = { | |||
isVisible: PropTypes.bool.isRequired, | |||
|
|||
/** Image crop vector mask */ | |||
maskImage: PropTypes.func, | |||
maskImage: PropTypes.oneOfType([PropTypes.func, imagePropTypes.source]), |
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.
Seems that this exact type is used in several places to indicate a field that accepts image component - maybe we could define this type within imagePropTypes
and reuse it?
|
||
return ( | ||
<View style={styles.walletCard}> | ||
<Image |
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.
Same as in other places, even though only this particular component differs between native and web, we have two big files that are mostly identical :(
Maybe we could create some component called <Image>
of our own and have two implementations of it depending on platform?
src/components/Image/index.native.js
Outdated
props.onLoad(evt); | ||
} | ||
}} | ||
// onLoad={(evt) => { |
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.
Remove usuned code
onLayout={this.onLayout} | ||
> | ||
<View style={styles.expensifyQrLogo}> | ||
<Image |
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.
ANother place with two almost identical files.
width={variables.modalTopIconWidth} | ||
height={props.is2FARequired ? variables.modalTopIconHeight : variables.modalTopBigIconHeight} | ||
src={props.is2FARequired ? Illustrations.SafeBlue : Illustrations.Abracadabra} | ||
name={props.is2FARequired ? 'Safe' : 'Abracadabra'} |
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.
Is Abracadabra intentional? :D
src/components/MentionSuggestions.js
Outdated
@@ -77,7 +76,7 @@ function MentionSuggestions(props) { | |||
size={isIcon ? CONST.AVATAR_SIZE.MENTION_ICON : CONST.AVATAR_SIZE.SMALLER} | |||
name={item.icons[0].name} | |||
type={item.icons[0].type} | |||
fill={themeColors.success} | |||
// fill={themeColors.success} |
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.
Unused code
src/components/MultipleAvatars.js
Outdated
@@ -137,7 +138,7 @@ function MultipleAvatars(props) { | |||
<Avatar | |||
source={props.icons[0].source} | |||
size={props.size} | |||
fill={themeColors.iconSuccessFill} | |||
// fill={themeColors.iconSuccessFill} |
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.
Unused code
src/components/RoomHeaderAvatars.js
Outdated
@@ -45,7 +44,7 @@ function RoomHeaderAvatars(props) { | |||
<Avatar | |||
source={props.icons[0].source} | |||
imageStyles={[styles.avatarLarge]} | |||
fill={themeColors.iconSuccessFill} | |||
// fill={themeColors.iconSuccessFill} |
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.
Unused code - 2 places in this file
src/components/SubscriptAvatar.js
Outdated
size={isSmall ? CONST.AVATAR_SIZE.SMALL_SUBSCRIPT : CONST.AVATAR_SIZE.SUBSCRIPT} | ||
fill={themeColors.iconSuccessFill} | ||
// fill={themeColors.iconSuccessFill} |
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.
Unused code
@@ -33,6 +33,7 @@ function GenericErrorPage({translate}) { | |||
<View style={styles.mb5}> | |||
<Icon | |||
src={Expensicons.Bug} | |||
name="Bug" |
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.
Very similar story again
<DragAndDropConsumer onDrop={onDrop}> | ||
<View style={[styles.receiptDropOverlay, styles.w100, styles.h100, styles.justifyContentCenter, styles.alignItemsCenter]}> | ||
<View style={styles.receiptImageWrapper(receiptImageTopPosition)}> | ||
<Image |
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.
SAme story - almost identical files
<View style={[styles.flex1]}> | ||
<View style={styles.pageWrapper}> | ||
<View style={[styles.settingsPageBody, styles.mb6, styles.alignItemsCenter]}> | ||
<Image |
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.
Once again, this is the only difference between this and index.js
tests/unit/SidebarOrderTest.js
Outdated
@@ -182,7 +182,7 @@ describe('Sidebar', () => { | |||
// Then there should be a pencil icon and report one should be the first one because putting a draft on the active report should change its location | |||
// in the ordered list | |||
.then(() => { | |||
const pencilIcon = screen.queryAllByTestId('Pencil Icon'); | |||
const pencilIcon = screen.queryAllByTestId('SvgPencil Icon'); |
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.
Are those the only two test files that uses images test ids?
Signed-off-by: Ashutosh Khanduala <[email protected]>
a9339c6
to
3f2f41b
Compare
Details
This PR improves the way of displaying images on mobile platforms. The most relevant changes are the removal of react-native-svg-transformer and the use expo-image to display images in the app. Previously all icons in .svg format were imported as a React components, what in result has negative influence on app's performance. Thanks to the usage of expo-image, we no longer need to transform svg icons and can use them directly by passing them to the source property of the Image component from 'expo-image' library.
Fixed Issues
Reduced number of rendered elements in the component tree and better rendering times.
Rendering SignInPage with react-native-svg on Android
Rendering SignInPage with expo-image on Android
There are not issues associated with this PR.
$
PROPOSAL:
Original Problem/Solution was posted here: https://expensify.slack.com/archives/C01GTK53T8Q/p1695892593681869
Tests
Offline tests
QA Steps
PR Author Checklist
### Fixed Issues
section aboveTests
sectionOffline steps
sectionQA steps
sectiontoggleReport
and notonIconClick
)myBool && <MyComponent />
.src/languages/*
files and using the translation methodWaiting for Copy
label for a copy review on the original GH to get the correct copy.STYLE.md
) were followedAvatar
, I verified the components usingAvatar
are working as expected)/** comment above it */
this
properly so there are no scoping issues (i.e. foronClick={this.submit}
the methodthis.submit
should be bound tothis
in the constructor)this
are necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);
ifthis.submit
is never passed to a component event handler likeonClick
)StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)
)Avatar
is modified, I verified thatAvatar
is working as expected in all cases)ScrollView
component to make it scrollable when more elements are added to the page.main
branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTest
steps.Screenshots/Videos
Android: Native
Screen.Recording.2023-11-03.at.16.06.14.mov
Android: mWeb Chrome
Screen.Recording.2023-11-06.at.11.29.16.mov
iOS: Native
Screen.Recording.2023-11-03.at.15.23.51.mov
iOS: mWeb Safari
Screen.Recording.2023-11-03.at.15.37.54.mov
MacOS: Chrome / Safari
Screen.Recording.2023-11-03.at.15.05.11.mov
MacOS: Desktop
Screen.Recording.2023-11-03.at.14.58.11.mov