Fix massive lag on Task Assignee Selection Modal #22095

Thanos30 · 2023-07-03T01:41:33Z

Details

Refactoring the functionality of TaskAssigneeSelectorModal. I removed the duplicate useEffect hook (both hooks were called initially, reducing performance) and I debounced the call to get the options.

Fixed Issues

$ #20075
PROPOSAL: #20075 (comment)

Tests

Click on FAB
Click on Assign Task
Fill in Title and Description
Click on Assignee
Start typing and verify there is not blocking huge lag

Verify that no errors appear in the JS console

Offline tests

Click on FAB
Click on Assign Task
Fill in Title and Description
Click on Assignee
Start typing and verify there is not blocking huge lag

QA Steps

Click on FAB
Click on Assign Task
Fill in Title and Description
Click on Assignee
Start typing and verify there is not blocking huge lag

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Web

Screen.Recording.2023-07-03.at.3.53.08.AM.mov

Mobile Web - Chrome

Screen.Recording.2023-07-03.at.3.56.05.AM.mov

Mobile Web - Safari

Screen.Recording.2023-07-03.at.3.56.05.AM.mov

Desktop

Screen.Recording.2023-07-03.at.4.04.57.AM.mov

iOS

Screen.Recording.2023-07-03.at.4.34.51.AM.mov

Android

Screen.Recording.2023-07-03.at.4.34.51.AM.mov

melvin-bot · 2023-07-03T01:41:37Z

@rushatgabhane 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]

francoisl · 2023-07-03T17:50:03Z

Hi @Thanos30, can you please run npm run prettier and then commit the changse? Thanks!

Thanos30 · 2023-07-03T18:39:30Z

Hi @Thanos30, can you please run npm run prettier and then commit the changse? Thanks!

Done, thank you for the tip @francoisl

rushatgabhane · 2023-07-03T18:54:19Z

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 / Chrome
- iOS / native
- iOS / 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 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-07-04.at.10.06.12.mov

Screen.Recording.2023-07-04.at.10.05.22.mov

Mobile Web - Chrome

WhatsApp.Video.2023-07-04.at.10.20.16.mp4

Mobile Web - Safari

Screen.Recording.2023-07-04.at.10.45.17.mov

Desktop

Screen.Recording.2023-07-04.at.10.15.52.mov

iOS

Screen.Recording.2023-07-04.at.10.43.09.mov

Android

Screen.Recording.2023-07-04.at.10.28.04.mp4

rushatgabhane · 2023-07-03T21:45:31Z

Hi @Thanos30 could we also debounce TaskShareDestinationSelectorModal please

It also uses useEffect twice

Thanos30 · 2023-07-04T00:14:21Z

Hi @Thanos30 could we also debounce TaskShareDestinationSelectorModal please

It also uses useEffect twice

Done @rushatgabhane , I made the debounce timeout smaller here, since I had the chance to work on TaskShareDestinationSelectorModal recently, and the options are less (we only want to show chats that have already been opened), and so are the computations.

rushatgabhane · 2023-07-04T04:41:49Z

cool, thanks for explaining that.

rushatgabhane

Nice work, LGTM!

francoisl · 2023-07-05T23:14:10Z

Hi, reviewing now - sorry I was OOO yesterday. Can you fix the conflict in TaskShareDestinationSelectorModal please?

…task-assignee-selection

Thanos30 · 2023-07-06T00:15:45Z

@francoisl No worries, I resolved the conflicts.

francoisl

LGMT and works well!

francoisl · 2023-07-06T01:05:37Z

src/pages/tasks/TaskShareDestinationSelectorModal.js

@@ -48,7 +48,6 @@ function TaskShareDestinationSelectorModal(props) {
    const [filteredPersonalDetails, setFilteredPersonalDetails] = useState([]);
    const [filteredUserToInvite, setFilteredUserToInvite] = useState(null);

-    // Filter out all the reports where user is not allowed to create task


Not blocking on this but there was no need to remove this comment, it was actually insightful.

Oh shoot, I must have missed that. I am sorry

OSBotify · 2023-07-06T01:10:15Z

✋ 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-07-07T10:45:33Z

🚀 Deployed to staging by https://github.com/francoisl in version: 1.3.38-0 🚀

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

OSBotify · 2023-07-11T00:00:35Z

🚀 Deployed to production by https://github.com/francoisl in version: 1.3.38-7 🚀

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

Fix massive lag on Task Assignee Selection Modal

64849f0

Thanos30 requested a review from a team as a code owner July 3, 2023 01:41

melvin-bot bot requested review from rushatgabhane and removed request for a team July 3, 2023 01:41

Prettify code

7693192

Apply the same logic to Share Destination

bfb3db9

Run npm run prettier

e01a4b2

rushatgabhane approved these changes Jul 4, 2023

View reviewed changes

melvin-bot bot requested a review from francoisl July 4, 2023 05:16

Merge remote-tracking branch 'upstream/main' into fix/massive-lag-on-…

158bdd9

…task-assignee-selection

francoisl approved these changes Jul 6, 2023

View reviewed changes

francoisl merged commit 0e21bc5 into Expensify:main Jul 6, 2023

OSBotify mentioned this pull request Jul 7, 2023

Deploy Checklist: New Expensify 2023-07-07 #22399

Closed

64 tasks

melvin-bot bot mentioned this pull request Jul 10, 2023

[HOLD for payment 2023-07-17] [$1000] In the Assign Task flow, when typing an assignee’s email, there is massive lag #20075

Closed

6 tasks

Fix massive lag on Task Assignee Selection Modal #22095

Fix massive lag on Task Assignee Selection Modal #22095

Uh oh!

Conversation

Thanos30 commented Jul 3, 2023

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Jul 3, 2023

Uh oh!

francoisl commented Jul 3, 2023

Uh oh!

Thanos30 commented Jul 3, 2023

Uh oh!

rushatgabhane commented Jul 3, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

rushatgabhane commented Jul 3, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Thanos30 commented Jul 4, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

rushatgabhane commented Jul 4, 2023

Uh oh!

rushatgabhane left a comment

Choose a reason for hiding this comment

Uh oh!

francoisl commented Jul 5, 2023

Uh oh!

Thanos30 commented Jul 6, 2023

Uh oh!

francoisl left a comment

Choose a reason for hiding this comment

Uh oh!

francoisl Jul 6, 2023

Choose a reason for hiding this comment

Uh oh!

Thanos30 Jul 6, 2023

Choose a reason for hiding this comment

Uh oh!

OSBotify commented Jul 6, 2023

Uh oh!

OSBotify commented Jul 7, 2023

Uh oh!

OSBotify commented Jul 11, 2023

Uh oh!

Uh oh!

rushatgabhane commented Jul 3, 2023 •

edited

Loading

rushatgabhane commented Jul 3, 2023 •

edited

Loading

Thanos30 commented Jul 4, 2023 •

edited

Loading