Skip to content

fix: Track seen logins to filter out duplicates in personal details #57459

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

Conversation

danstepanov
Copy link
Contributor

@danstepanov danstepanov commented Feb 26, 2025

Explanation of Change

Optimized the filtering of personal details in mention suggestions by using a Set to track duplicate logins instead of using array.findIndex. This visibly improves performance and fixes flickering issues when typing @ in the composer, particularly noticeable with large numbers of personal details. This issue only pertains to iOS.

Fixed Issues

$ #54991
PROPOSAL: #54991 (comment)

Tests

  1. Authenticate with the Applause test account
  2. Open any chat or room with multiple participants (preferably a workspace with many members)
  3. Type @ in the composer
  4. Verify the mention suggestions menu appears smoothly without flickering and in a timely fashion
  5. Type additional characters to filter the suggestions
  6. Verify the menu updates smoothly without flickering or lag
  7. Select a suggestion and verify it's inserted correctly
  8. Verify that duplicate logins are still properly filtered out
  • Verify that no errors appear in the JS console

Offline tests

No offline testing needed as this is a UI performance optimization.

QA Steps

Sam as tests

  • Verify that no errors appear in the JS console

PR Author 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 that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • 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 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 either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • 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.ts 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
      • 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(theme.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 the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • 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.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • 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

Android: Native

Before
https://github.com/user-attachments/assets/741eef7a-504d-4cae-8c6c-382df043d6da

After
https://github.com/user-attachments/assets/bf633fc7-f211-4686-9852-9640ae10f47e

Android: mWeb Chrome

Before
https://github.com/user-attachments/assets/741eef7a-504d-4cae-8c6c-382df043d6da

After
https://github.com/user-attachments/assets/bf633fc7-f211-4686-9852-9640ae10f47e

iOS: Native

Before
https://github.com/user-attachments/assets/741eef7a-504d-4cae-8c6c-382df043d6da

After
https://github.com/user-attachments/assets/bf633fc7-f211-4686-9852-9640ae10f47e

iOS: mWeb Safari

Before
https://github.com/user-attachments/assets/741eef7a-504d-4cae-8c6c-382df043d6da

After
https://github.com/user-attachments/assets/bf633fc7-f211-4686-9852-9640ae10f47e

MacOS: Chrome / Safari

Before
https://github.com/user-attachments/assets/741eef7a-504d-4cae-8c6c-382df043d6da

After
https://github.com/user-attachments/assets/bf633fc7-f211-4686-9852-9640ae10f47e

MacOS: Desktop

Before
https://github.com/user-attachments/assets/741eef7a-504d-4cae-8c6c-382df043d6da

After
https://github.com/user-attachments/assets/bf633fc7-f211-4686-9852-9640ae10f47e

Copy link
Contributor

github-actions bot commented Feb 26, 2025

All contributors have signed the CLA ✍️ ✅
Posted by the CLA Assistant Lite bot.

@danstepanov danstepanov marked this pull request as ready for review February 27, 2025 08:20
@danstepanov danstepanov requested a review from a team as a code owner February 27, 2025 08:20
@melvin-bot melvin-bot bot requested review from abdulrahuman5196 and removed request for a team February 27, 2025 08:20
Copy link

melvin-bot bot commented Feb 27, 2025

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

@luacmartins
Copy link
Contributor

@danstepanov please follow the steps here to sign the CLA

@danstepanov
Copy link
Contributor Author

I have read the CLA Document and I hereby sign the CLA

CLABotify added a commit to Expensify/CLA that referenced this pull request Feb 28, 2025
@danstepanov
Copy link
Contributor Author

@abdulrahuman5196 do you have time to add the requisite videos (presumably just android native?). I am currently busy with other tasks.

@danstepanov danstepanov force-pushed the @danstepanov/fix/slow-response-mention-suggestion branch from 437fed3 to 6e93955 Compare February 28, 2025 05:13
@danstepanov danstepanov force-pushed the @danstepanov/fix/slow-response-mention-suggestion branch from 1d10e3c to da39f89 Compare February 28, 2025 05:39
@danstepanov
Copy link
Contributor Author

I have some additional changes I'd like to make to this that would further improve performance but, in the interest of moving onto other tasks, this does solve the problem.

@hannojg
Copy link
Contributor

hannojg commented Feb 28, 2025

Thats sounds good, we usually create a follow up issue ticket for that!
(let me create one …)

tsconfig.json Outdated
@@ -22,7 +22,8 @@
"@styles/*": ["./src/styles/*"],
"@src/*": ["./src/*"],
"@userActions/*": ["./src/libs/actions/*"]
}
},
"jsx": "react-jsx"
Copy link
Member

Choose a reason for hiding this comment

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

what does this exactly do?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

not sure why I didn't get these notifications but I made this change for reasons unrelated directly to this PR, I can remove it. I was running into Typescript issues while working on the issue and this seemed to resolve them. This has to do with how JSX is transformed in TS files.

tsconfig.json Outdated
@@ -22,7 +22,8 @@
"@styles/*": ["./src/styles/*"],
"@src/*": ["./src/*"],
"@userActions/*": ["./src/libs/actions/*"]
}
},
"jsx": "react-jsx"
Copy link
Contributor

Choose a reason for hiding this comment

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

This change seems unrelated to this pr, can you please remove it?

tsconfig.json Outdated
@@ -22,7 +22,8 @@
"@styles/*": ["./src/styles/*"],
"@src/*": ["./src/*"],
"@userActions/*": ["./src/libs/actions/*"]
}
},
"jsx": "react-jsx"
Copy link
Contributor

Choose a reason for hiding this comment

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

This shouldn't be needed here. Please remove it as said above ^

Copy link
Contributor

Choose a reason for hiding this comment

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

@danstepanov Bump on this one

Copy link
Contributor Author

Choose a reason for hiding this comment

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

sorry for the delay here, I'm just seeing these messages. I've removed the change.

@lakchote lakchote requested review from DylanDylann and removed request for abdulrahuman5196 March 3, 2025 06:28
@lakchote
Copy link
Contributor

lakchote commented Mar 3, 2025

@DylanDylann
Copy link
Contributor

Thanks. I will start on this today

@DylanDylann
Copy link
Contributor

One redundant change, the rest looks fine.

@DylanDylann
Copy link
Contributor

@danstepanov Ops.... While testing on some chats, I see that this problem still happens on IOS

Screen.Recording.2025-03-03.at.16.55.10.mov

@DylanDylann
Copy link
Contributor

DylanDylann commented Mar 3, 2025

From my investigation, the suggestion list doesn't display because of this check

if ((containerState.width === 0 && containerState.left === 0 && containerState.bottom === 0) || (containerState.cursorCoordinates.x === 0 && containerState.cursorCoordinates.y === 0)) {
return null;
}

From my log, I see that:

cursorCoordinates {"x": 0, "y": 0}

@danstepanov danstepanov force-pushed the @danstepanov/fix/slow-response-mention-suggestion branch from 8f38734 to 0c00b31 Compare March 7, 2025 10:17
@DylanDylann
Copy link
Contributor

@danstepanov I think we also need to revert these changes

Screenshot 2025-03-07 at 18 21 53

});
});
}, [measureParentContainerAndReportCursor, windowHeight, windowWidth, keyboardHeight, shouldUseNarrowLayout, suggestionsLength, bottomInset, topInset, isKeyboardAnimatingRef]);

if ((containerState.width === 0 && containerState.left === 0 && containerState.bottom === 0) || (containerState.cursorCoordinates.x === 0 && containerState.cursorCoordinates.y === 0)) {
// Only prevent rendering if we have no suggestions
Copy link
Contributor

Choose a reason for hiding this comment

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

This comment doesn't reflect all below conditions

@@ -134,14 +146,16 @@ function AutoCompleteSuggestions<TSuggestion>({measureParentContainerAndReportCu
left: leftValue.current,
bottom: bottomValue,
width: widthValue,
cursorCoordinates,
cursorCoordinates: {x: cursorCoordinates.x, y: cursorCoordinates.y},
Copy link
Contributor

Choose a reason for hiding this comment

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

@danstepanov One more place, please revert it

@DylanDylann
Copy link
Contributor

DylanDylann commented Mar 11, 2025

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 either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • 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(theme.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 the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • 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

Android: Native
Screen.Recording.2025-03-11.at.16.58.36.mov
Android: mWeb Chrome
Screen.Recording.2025-03-11.at.17.01.15.mov
iOS: Native
Screen.Recording.2025-03-11.at.16.59.17.mov
iOS: mWeb Safari
Screen.Recording.2025-03-11.at.17.00.17.mov
MacOS: Chrome / Safari
Screen.Recording.2025-03-11.at.17.02.38.mov
MacOS: Desktop
Screen.Recording.2025-03-11.at.17.01.58.mov

@melvin-bot melvin-bot bot requested a review from lakchote March 11, 2025 16:13
@DylanDylann
Copy link
Contributor

@lakchote Minor suggested change here. All rest looks fine to me

Copy link
Contributor

@lakchote lakchote left a comment

Choose a reason for hiding this comment

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

@danstepanov please address comment here to make things consistent. Other than that LGTM

@melvin-bot melvin-bot bot requested a review from lakchote March 13, 2025 02:48
@danstepanov danstepanov requested a review from mountiny March 13, 2025 05:08
Copy link
Contributor

@lakchote lakchote left a comment

Choose a reason for hiding this comment

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

LGTM. @mountiny if you want to check it

@mountiny mountiny dismissed their stale review March 14, 2025 00:15

Addressed

@mountiny
Copy link
Contributor

All good, not reviewing but going to merge as you approved

@mountiny mountiny merged commit bd8809d into Expensify:main Mar 14, 2025
18 checks passed
@OSBotify
Copy link
Contributor

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

Copy link
Contributor

🚀 Deployed to staging by https://github.com/mountiny in version: 9.1.13-0 🚀

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

@mountiny
Copy link
Contributor

@danstepanov @DylanDylann Can you please follow up, seems like its not fixed thanks!

@DylanDylann
Copy link
Contributor

@kavimuru This appears to be inconsistent across accounts. If possible, could you export your Onyx data? That way, we can take a deeper look into it and assist you further.

Copy link
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 9.1.13-5 🚀

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

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.

9 participants