perf: Implement filtering in New Chat page #40350

TMisiukiewicz · 2024-04-17T12:46:28Z

Details

This is the continuation of moving from getSearchText to filtering the lists. Here we are migrating the logic in New Chat page

Fixed Issues

$ #44634
PROPOSAL:

Tests

Press global create and select "New chat"
Type something that matches any of the options existing on your list
Verify option is displayed after finished typing
Verify the list has the same options in the same order as the same search text applied on main branch
Clean the input and type a random email that does not exist on the list
Verify the email appears on the list if it's valid

Verify that no errors appear in the JS console

Offline tests

n/a

QA Steps

Press global create and select "New chat"
Type something that matches any of the options existing on your list
Verify option is displayed after finished typing
Clean the input and type a random email that does not exist on the list
Verify the email appears on the list if it's valid

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Screen.Recording.2024-06-25.at.14.56.43.mov

Android: mWeb Chrome

ANDROID.WEB.mov

iOS: Native

Simulator.Screen.Recording.-.iPhone.15.Pro.-.2024-06-25.at.14.25.08.mp4

iOS: mWeb Safari

IOS.WEB.mp4

MacOS: Chrome / Safari

WEB.mov

MacOS: Desktop

DESKTOP.mov

TMisiukiewicz · 2024-04-17T12:47:02Z

To be opened once #40235 gets merged - it's sharing the same logic for inviting a user as in the mentioned PR

melvin-bot · 2024-06-25T12:58:24Z

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

hungvu193 · 2024-06-25T13:37:23Z

I'm seeing you linked closed issue. Is that correct PR? 🤯

TMisiukiewicz · 2024-06-26T06:06:44Z

@hungvu193 this PR (and a few others) was in draft for pretty long time because it was waiting for #40235 to be merged first. I can see the issue was closed after merging it during my PTO 🤔 What should we do then? Should we create a new issue to link all of those PRs?

hungvu193 · 2024-06-26T06:27:27Z

I think we should create another issue for this PR, Yes.
Let's me approve to pull internal engineer here.

hungvu193 · 2024-06-26T06:28:20Z

@roryabraham Can you take a look at the comment above? TIA

roryabraham · 2024-06-28T17:36:20Z

@hungvu193 created #44634 for this. @TMisiukiewicz can you please comment for assignment?

TMisiukiewicz · 2024-07-01T06:14:40Z

@roryabraham commented and updated issue in the PR description, thank you 👍

hungvu193 · 2024-07-01T09:39: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: 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

Android.mov

Android: mWeb Chrome

Screen.Recording.2024-07-01.at.16.38.20.mov

iOS: Native

ios.mov

iOS: mWeb Safari

mSAfari.mov

MacOS: Chrome / Safari

Chrome.mov

MacOS: Desktop

desktop.mov

hungvu193

Tests well 🎉

TMisiukiewicz · 2024-07-08T06:42:48Z

updated branch with latest main

OSBotify · 2024-07-09T18:35:30Z

✋ 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 · 2024-07-10T11:19:02Z

🚀 Deployed to staging by https://github.com/roryabraham in version: 9.0.6-0 🚀

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

OSBotify · 2024-07-10T11:36:16Z

🚀 Deployed to staging by https://github.com/roryabraham in version: 9.0.6-0 🚀

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

OSBotify · 2024-07-11T10:16:31Z

🚀 Cherry-picked to staging by https://github.com/Julesssss in version: 9.0.6-1 🚀

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

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

OSBotify · 2024-07-11T10:36:07Z

🚀 Cherry-picked to staging by https://github.com/Julesssss in version: 9.0.6-1 🚀

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

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

OSBotify · 2024-07-15T20:17:47Z

🚀 Deployed to production by https://github.com/thienlnam in version: 9.0.6-8 🚀

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

OSBotify · 2024-07-17T00:17:25Z

🚀 Deployed to production by https://github.com/thienlnam in version: 9.0.7-8 🚀

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

implement filtering in new chat page

fbabcb9

TMisiukiewicz added 4 commits June 25, 2024 11:28

Merge branch 'main' into perf/new-chat-page-filtering

18128de

remove max participants

59e70fe

display selfDM in new chat

fc30cb2

Merge branch 'main' into perf/new-chat-page-filtering

16a2ec4

TMisiukiewicz marked this pull request as ready for review June 25, 2024 12:58

TMisiukiewicz requested a review from a team as a code owner June 25, 2024 12:58

melvin-bot bot requested review from hungvu193 and removed request for a team June 25, 2024 12:58

hungvu193 approved these changes Jun 26, 2024

View reviewed changes

melvin-bot bot requested a review from roryabraham June 26, 2024 06:27

This was referenced Jun 26, 2024

perf: filter Share Logs options #40285

Merged

perf: Intive to workspace options filtering #40793

Merged

roryabraham mentioned this pull request Jun 28, 2024

[HOLD for payment 2024-07-24][$250] Improve filtering performance in new chat page #44634

Closed

hungvu193 approved these changes Jul 1, 2024

View reviewed changes

Merge branch 'main' into perf/new-chat-page-filtering

7f237be

roryabraham approved these changes Jul 9, 2024

View reviewed changes

roryabraham merged commit 1b9ed26 into Expensify:main Jul 9, 2024
15 checks passed

github-actions bot mentioned this pull request Jul 10, 2024

Deploy Checklist: New Expensify 2024-07-10 #45144

Closed

eh2077 mentioned this pull request Sep 19, 2024

[HOLD for payment 2024-10-29] [$250] Submit Expense - Contacts section is missing participants #48114

Closed

6 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

perf: Implement filtering in New Chat page #40350

perf: Implement filtering in New Chat page #40350

TMisiukiewicz commented Apr 17, 2024 •

edited

Loading

TMisiukiewicz commented Apr 17, 2024 •

edited

Loading

melvin-bot bot commented Jun 25, 2024

hungvu193 commented Jun 25, 2024

TMisiukiewicz commented Jun 26, 2024

hungvu193 commented Jun 26, 2024

hungvu193 commented Jun 26, 2024

roryabraham commented Jun 28, 2024

TMisiukiewicz commented Jul 1, 2024

hungvu193 commented Jul 1, 2024

hungvu193 left a comment

TMisiukiewicz commented Jul 8, 2024

OSBotify commented Jul 9, 2024

OSBotify commented Jul 10, 2024

OSBotify commented Jul 10, 2024

OSBotify commented Jul 11, 2024

OSBotify commented Jul 11, 2024

OSBotify commented Jul 15, 2024

OSBotify commented Jul 17, 2024

perf: Implement filtering in New Chat page #40350

perf: Implement filtering in New Chat page #40350

Conversation

TMisiukiewicz commented Apr 17, 2024 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

TMisiukiewicz commented Apr 17, 2024 • edited Loading

melvin-bot bot commented Jun 25, 2024

hungvu193 commented Jun 25, 2024

TMisiukiewicz commented Jun 26, 2024

hungvu193 commented Jun 26, 2024

hungvu193 commented Jun 26, 2024

roryabraham commented Jun 28, 2024

TMisiukiewicz commented Jul 1, 2024

hungvu193 commented Jul 1, 2024

Reviewer Checklist

Screenshots/Videos

hungvu193 left a comment

Choose a reason for hiding this comment

TMisiukiewicz commented Jul 8, 2024

OSBotify commented Jul 9, 2024

OSBotify commented Jul 10, 2024

OSBotify commented Jul 10, 2024

OSBotify commented Jul 11, 2024

OSBotify commented Jul 11, 2024

OSBotify commented Jul 15, 2024

OSBotify commented Jul 17, 2024

TMisiukiewicz commented Apr 17, 2024 •

edited

Loading

TMisiukiewicz commented Apr 17, 2024 •

edited

Loading