[Perf] ReportScreen rendering optimisation #30063

kacper-mikolajczak · 2023-10-20T09:39:03Z

Details

Fixed Issues

$ #29987
PROPOSAL: #29987

Tests

Verify that no errors appear in the JS console

Open report screen
Scroll list of messages
React to the message, see if the list is updated correctly
Send a message, see if the list is updated correctly

Offline tests

N/A

QA Steps

Verify that no errors appear in the JS console

Open report screen
Scroll list of messages
React to the message, see if the list is updated correctly
Send a message, see if the list is updated correctly

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 / Chrome
- iOS / native
- iOS / 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

android.mp4

Android: mWeb Chrome

mandroid.mp4

iOS: Native

ios.mp4

iOS: mWeb Safari

mios.mp4

MacOS: Chrome / Safari

web.mp4

MacOS: Desktop

desktop.mp4

adhorodyski · 2023-10-20T11:24:53Z

src/components/OnyxProvider.tsx

@@ -6,7 +6,7 @@ import ComposeProviders from './ComposeProviders';
 // Set up any providers for individual keys. This should only be used in cases where many components will subscribe to
 // the same key (e.g. FlatList renderItem components)
 const [withNetwork, NetworkProvider, NetworkContext] = createOnyxContext(ONYXKEYS.NETWORK);
-const [withPersonalDetails, PersonalDetailsProvider] = createOnyxContext(ONYXKEYS.PERSONAL_DETAILS_LIST);
+const [withPersonalDetails, PersonalDetailsProvider, , usePersonalDetails] = createOnyxContext(ONYXKEYS.PERSONAL_DETAILS_LIST);


100% intentional? just asking :P

Haha, good catch! ^^ Edu asked the same here.

tl;dr; It is intentional as the context value is no needed and eslint did not allow _ as a placeholder - so we stick to this - perfectly valid, although quirky syntax :D

yeah, a valid syntax that looks like a poorly resolved conflict 😂 Thanks!

just wanted to make sure, fine with me then :)

TIL

FWIW I think it might be more obvious to use the eslint disable. This looks really weird to me 😄

Yup the syntax is quite peculiar :D Wonder if there is an option in eslint to let us use _ as a placeholder (if I am not mistaken such syntax is used for example in Python).

I am not really a big fan of adding eslint disable comments ^^

Where there is a will there is a Stack Overflow! 🎉

@marcaaron Let people decide! :D

src/pages/home/report/ReportActionItem.js

src/pages/home/report/ReportActionItemSingle.js

…JECT

melvin-bot · 2023-10-20T11:47:54Z

@eVoloshchak Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

eVoloshchak · 2023-10-23T14:45:46Z

@kacper-mikolajczak, could you merge the latest main?
There are conflicts and a failing test (which doesn't seem related to this PR, so should also be resolved when pulling main)

kacper-mikolajczak · 2023-10-23T15:20:05Z

@eVoloshchak done 👍

eVoloshchak · 2023-10-23T15:50:46Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified tests pass on all platforms & I tested again on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (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
- 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 verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
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
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
- 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 reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Screen.Recording.2023-10-23.at.18.32.05.mov

Mobile Web - Chrome

screen-20231023-182902.mp4

Mobile Web - Safari

Screen.Recording.2023-10-23.at.18.30.25.mov

Desktop

Screen.Recording.2023-10-23.at.18.33.47.mov

iOS

Screen.Recording.2023-10-23.at.18.25.12.mov

Android

screen-20231023-182417.mp4

eVoloshchak

Wow, this is visibly faster, even without any measurements. On Android with HT account the difference is especially noticeable

thienlnam

This is great!

OSBotify · 2023-10-23T17:44:32Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

OSBotify · 2023-10-24T02:00:08Z

🚀 Deployed to staging by https://github.com/thienlnam in version: 1.3.90-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

kacper-mikolajczak · 2023-10-24T09:04:46Z

Good to hear that guys, thanks!

OSBotify · 2023-10-25T16:37:02Z

🚀 Deployed to production by https://github.com/marcaaron in version: 1.3.90-2 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	failure ❌
🕸 web 🕸	success ✅

OSBotify · 2023-10-25T17:01:50Z

🚀 Deployed to staging by https://github.com/thienlnam in version: 1.3.91-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

OSBotify · 2023-10-26T22:43:51Z

🚀 Deployed to production by https://github.com/marcaaron in version: 1.3.91-8 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

kacper-mikolajczak added 4 commits October 20, 2023 11:22

add useOnyxContext hook

61f7064

ReportActionItem swap withPersonalDetails to usePersonalDetails

93f9ac7

ReportActionItemSingle swap withPersonalDetails to usePersonalDetails

0ff1605

withCurrentUserPersonalDetails swap withOnyx to usePersonalDetails

946ad2b

kacper-mikolajczak mentioned this pull request Oct 20, 2023

ReportScreen rendering optimisation #29815

Closed

59 tasks

kacper-mikolajczak added 2 commits October 20, 2023 13:22

withCurrentUserPersonalDetails add default value for back-compat

946d764

add default values for back-compat

e363e00

adhorodyski reviewed Oct 20, 2023

View reviewed changes

src/pages/home/report/ReportActionItem.js Outdated Show resolved Hide resolved

adhorodyski reviewed Oct 20, 2023

View reviewed changes

src/pages/home/report/ReportActionItemSingle.js Show resolved Hide resolved

replace inline instances of empty object with a reference to EMPTY_OB…

df96e09

…JECT

kacper-mikolajczak requested a review from adhorodyski October 20, 2023 11:32

adhorodyski approved these changes Oct 20, 2023

View reviewed changes

kacper-mikolajczak marked this pull request as ready for review October 20, 2023 11:47

kacper-mikolajczak requested a review from a team as a code owner October 20, 2023 11:47

melvin-bot bot removed the request for review from a team October 20, 2023 11:47

melvin-bot bot requested a review from eVoloshchak October 20, 2023 11:47

kacper-mikolajczak added a commit to kacper-mikolajczak/ExpensifyApp that referenced this pull request Oct 23, 2023

use solution from Expensify#30063

ff1592d

Merge branch 'main' into perf/report-screen/tti

1850885

eVoloshchak approved these changes Oct 23, 2023

View reviewed changes

melvin-bot bot requested a review from thienlnam October 23, 2023 16:41

thienlnam approved these changes Oct 23, 2023

View reviewed changes

thienlnam merged commit 9dd2eff into Expensify:main Oct 23, 2023
12 checks passed

OSBotify mentioned this pull request Oct 24, 2023

Deploy Checklist: New Expensify 2023-10-24 #30224

Closed

43 tasks

melvin-bot bot mentioned this pull request Oct 25, 2023

[HOLD for payment 2023-11-17] [Performance] ReportScreen loading times #29987

Closed

OSBotify mentioned this pull request Oct 25, 2023

Deploy Checklist: New Expensify 2023-10-25 #30365

Closed

99 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Perf] ReportScreen rendering optimisation #30063

[Perf] ReportScreen rendering optimisation #30063

kacper-mikolajczak commented Oct 20, 2023 •

edited

Loading

adhorodyski Oct 20, 2023

kacper-mikolajczak Oct 20, 2023

adhorodyski Oct 20, 2023

adhorodyski Oct 20, 2023

kacper-mikolajczak Oct 20, 2023

marcaaron Oct 25, 2023

kacper-mikolajczak Oct 26, 2023

marcaaron Oct 26, 2023

kacper-mikolajczak Oct 27, 2023 •

edited

Loading

melvin-bot bot commented Oct 20, 2023

eVoloshchak commented Oct 23, 2023

kacper-mikolajczak commented Oct 23, 2023

eVoloshchak commented Oct 23, 2023 •

edited

Loading

eVoloshchak left a comment

thienlnam left a comment

OSBotify commented Oct 23, 2023

OSBotify commented Oct 24, 2023

kacper-mikolajczak commented Oct 24, 2023

OSBotify commented Oct 25, 2023

OSBotify commented Oct 25, 2023

OSBotify commented Oct 26, 2023

[Perf] ReportScreen rendering optimisation #30063

[Perf] ReportScreen rendering optimisation #30063

Conversation

kacper-mikolajczak commented Oct 20, 2023 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

kacper-mikolajczak Oct 27, 2023 • edited Loading

Choose a reason for hiding this comment

melvin-bot bot commented Oct 20, 2023

eVoloshchak commented Oct 23, 2023

kacper-mikolajczak commented Oct 23, 2023

eVoloshchak commented Oct 23, 2023 • edited Loading

Reviewer Checklist

Screenshots/Videos

eVoloshchak left a comment

Choose a reason for hiding this comment

thienlnam left a comment

Choose a reason for hiding this comment

OSBotify commented Oct 23, 2023

OSBotify commented Oct 24, 2023

kacper-mikolajczak commented Oct 24, 2023

OSBotify commented Oct 25, 2023

OSBotify commented Oct 25, 2023

OSBotify commented Oct 26, 2023

kacper-mikolajczak commented Oct 20, 2023 •

edited

Loading

kacper-mikolajczak Oct 27, 2023 •

edited

Loading

eVoloshchak commented Oct 23, 2023 •

edited

Loading