Skip to content
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

Merged
merged 115 commits into from
Dec 22, 2023
Merged

Expo image #4

merged 115 commits into from
Dec 22, 2023

Conversation

WojtekBoman
Copy link

@WojtekBoman WojtekBoman commented Oct 16, 2023

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 Screenshot 2023-11-02 at 15 46 52
Rendering SignInPage with expo-image on Android Screenshot 2023-11-02 at 15 46 15

There are not issues associated with this PR.
$
PROPOSAL:
Original Problem/Solution was posted here: https://expensify.slack.com/archives/C01GTK53T8Q/p1695892593681869

Tests

  1. Go through the application and check for any problems with displaying images
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

  1. Go through the application and check for any problems with displaying images
  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
    • MacOS: Desktop
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

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

@WojtekBoman WojtekBoman force-pushed the expo-image branch 3 times, most recently from af156f6 to ba026f7 Compare October 17, 2023 08:57
};

type AssetIcon = {
icon: React.FC<SvgProps>;

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.

contentFit: PropTypes.string,

/** Is icon displayed in its own color */
displayInDefaultIconColor: PropTypes.bool,

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.

Copy link
Author

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.

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

Copy link
Author

@WojtekBoman WojtekBoman Oct 18, 2023

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

name: PropTypes.string,

/** Determines how the image should be resized to fit its container */
contentFit: PropTypes.string,

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?

Copy link
Author

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

style={[StyleUtils.getWidthAndHeightStyle(width, height), styles.bgTransparent, styles.overflowVisible]}
>
<View style={iconStyles}>
<Image

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]),

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

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?

props.onLoad(evt);
}
}}
// onLoad={(evt) => {

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

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'}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is Abracadabra intentional? :D

@@ -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}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unused code

@@ -137,7 +138,7 @@ function MultipleAvatars(props) {
<Avatar
source={props.icons[0].source}
size={props.size}
fill={themeColors.iconSuccessFill}
// fill={themeColors.iconSuccessFill}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unused code

@@ -45,7 +44,7 @@ function RoomHeaderAvatars(props) {
<Avatar
source={props.icons[0].source}
imageStyles={[styles.avatarLarge]}
fill={themeColors.iconSuccessFill}
// fill={themeColors.iconSuccessFill}

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

size={isSmall ? CONST.AVATAR_SIZE.SMALL_SUBSCRIPT : CONST.AVATAR_SIZE.SUBSCRIPT}
fill={themeColors.iconSuccessFill}
// fill={themeColors.iconSuccessFill}

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"

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

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

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

@@ -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');

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?

BartoszGrajdek pushed a commit that referenced this pull request Oct 18, 2023
Signed-off-by: Ashutosh Khanduala <[email protected]>
@WojtekBoman WojtekBoman force-pushed the expo-image branch 2 times, most recently from a9339c6 to 3f2f41b Compare October 24, 2023 09:38
@BartoszGrajdek BartoszGrajdek merged commit 9c46375 into main Dec 22, 2023
11 of 14 checks passed
cdOut pushed a commit that referenced this pull request Sep 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants