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

Add new SearchButton to all pages and tweak SearchRouter #49379

Merged

Conversation

Kicu
Copy link
Contributor

@Kicu Kicu commented Sep 18, 2024

Details

  • This PR both implements issue xxx and also introduces some followups after merging SearchRouter (Add SearchRouter component and context to display it #48785)
  • SearchButton is added to almost every page (as listed in the design doc)
  • there is one exception: rooms list on mobile - because we still have the ChatFinder there, so this time I'm avoiding two search icons; ChatFinder will be removed in a separate issue
  • I had to add 1 prop to SelectionList to pass it to useKeyboardShortcut hook, since you can trigger search from router via Enter key, but useKeyboardShortcut consumed the ENTER keypress event

misc notes:

  • [tweaks] standardised naming of some SearchUtils functions; dropped one function that was only used in once place
  • WorkspacesListPage and TroubleShootPage were migrated to useOnyx in compliance with new CI check

Fixed Issues

$ #49122
$ #49118
PROPOSAL:

Tests

  • verify that the button to trigger new search is displayed on every page
  • verify that clicking the button opens new search router
  • verify that search router works - it should navigate to search with specific query

Offline tests

QA Steps

  • verify that the button to trigger new search is displayed on every page
  • verify that clicking the button opens new search router
  • verify that search router works - it should navigate to search with specific query

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 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 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 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.

Screenshots/Videos

Android: Native
rec-andr-searchb.mp4
Android: mWeb Chrome
iOS: Native
rec-ios-searchb.mp4
iOS: mWeb Safari https://github.com/user-attachments/assets/e9eb66ff-03af-4fde-a497-8770b7c6dff5
MacOS: Chrome / Safari
rec-web-searchb.mp4
MacOS: Desktop

@Kicu Kicu changed the title WIP prefill Search Router with existing Search query Add new SearchButton to all pages and tweak SearchRouter Sep 20, 2024
@@ -407,6 +397,20 @@ function getQueryHashFromString(query: SearchQueryString): number {
return UserUtils.hashText(query, 2 ** 32);
}

function getExpenseTypeTranslationKey(expenseType: ValueOf<typeof CONST.SEARCH.TRANSACTION_TYPE>): TranslationPaths {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

only moved

* @private
* traverses the AST and returns filters as a QueryFilters object
*/
function getFilters(queryJSON: SearchQueryJSON) {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

only moved

@Kicu Kicu marked this pull request as ready for review September 20, 2024 13:43
@Kicu Kicu requested a review from a team as a code owner September 20, 2024 13:43
@melvin-bot melvin-bot bot requested review from ikevin127 and removed request for a team September 20, 2024 13:43
Copy link

melvin-bot bot commented Sep 20, 2024

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

@Kicu
Copy link
Contributor Author

Kicu commented Sep 20, 2024

@luacmartins originally I planned for this PR to be something else, but now the scope changed a bit.
Ready for review

I'll check why reassure tests fail on Monday

@ikevin127
Copy link
Contributor

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.webm
Android: mWeb Chrome

Uploading android-mweb.mov…

iOS: Native
ios.mp4
iOS: mWeb Safari
ios-mweb.mp4
MacOS: Chrome / Safari
web.mov
MacOS: Desktop
desktop.mov

@ikevin127
Copy link
Contributor

Note

Observations

  1. Missing 🔍 in Settings > Subscription page (probably on purpose ?).
  2. When search input was performed and user is navigated to search page with specific query > 🔍 is missing from Filters button right side on wide layout devices (web / desktop).
  3. (already present on staging) When search input was performed and user is navigated to search page with specific query > LHN Expenses menu item is not highlighted.

Please confirm whether all of the above are expected.
Once addressed and the reassure tests are fixed, I'll be able to 🟢 Approve.

@luacmartins
Copy link
Contributor

Missing 🔍 in Settings > Subscription page (probably on purpose ?).

I think it should be present there too.

When search input was performed and user is navigated to search page with specific query > 🔍 is missing from Filters button right side on wide layout devices (web / desktop).

I think this one is expected for now, since those pages will have a full width search bar instead of the magnifying glass icon

(already present on staging) When search input was performed and user is navigated to search page with specific query > LHN Expenses menu item is not highlighted.

This is expected since at that point the user is seeing a custom search

@luacmartins
Copy link
Contributor

@Expensify/design should the magnifying glass icon be to the left or right of existing header buttons? example:

Screenshot 2024-09-23 at 9 10 05 AM

@dubielzyk-expensify
Copy link
Contributor

@Expensify/design should the magnifying glass icon be to the left or right of existing header buttons? example:

Great question. I think we'll always want it on the right to ensure the router stays consistently in the top right corner when it opens.

@Kicu
Copy link
Contributor Author

Kicu commented Sep 23, 2024

I think we'll always want it on the right to ensure the router stays consistently in the top right corner when it opens.

Yeah I made a similar assumption and I'm always putting it furthest to the right on all the views.

@Kicu
Copy link
Contributor Author

Kicu commented Sep 23, 2024

@ikevin127 @luacmartins icon added to Subscription page

Screenshot 2024-09-23 at 13 16 39

As for the other two like Carlos said they are expected. LHN items are only highglighted when you are on the exact query that the buttons link to, so type:Expenses status:all etc.

There is a separate PR to add full width input to Search Results page, and that is why we don't need 🔍 there. (See #49462)

Copy link
Contributor

@ikevin127 ikevin127 left a comment

Choose a reason for hiding this comment

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

🟢 This is looking good, I just verified that the search button was added to the Subscription page.

@Kicu ⚠️ The only thing left to do here is address the failing performance tests, which from what I can see the issue might come from the permissions check in SearchButton which does not seem to be mocked given the error message of the failing performance test:

● [ReportScreen] should render report list

    TypeError: _Permissions.default.canUseNewSearchRouter is not a function

      15 |     const {openSearchRouter} = useSearchRouterContext();
      16 |
    > 17 |     if (!Permissions.canUseNewSearchRouter()) {
         |                      ^
      18 |         return;
      19 |     }
      20 |

luacmartins
luacmartins previously approved these changes Sep 24, 2024
Copy link
Contributor

@luacmartins luacmartins left a comment

Choose a reason for hiding this comment

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

LGTM

@luacmartins
Copy link
Contributor

luacmartins commented Sep 24, 2024

Unrelated jest tests are failing on main too. Gonna wait for a fix before we merge this PR.

@Kicu
Copy link
Contributor Author

Kicu commented Sep 24, 2024

Main merged and the missing mock in perf tests fixed, thanks for pointing this out @ikevin127

Now the Changed files ESLint check is failing, but we can ignore this one. It fails on the deprecation of measurePerformance (because I touched *.perf-test file) which is not something we are concerned with right now.

If nothing else fails then I think we're good to go.

@luacmartins
Copy link
Contributor

Failing tests are unrelated to the changes in this PR, merging.

@luacmartins luacmartins merged commit 2ea2b15 into Expensify:main Sep 24, 2024
16 of 17 checks passed
Copy link

melvin-bot bot commented Sep 24, 2024

@luacmartins looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

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

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/luacmartins in version: 9.0.40-0 🚀

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

Copy link
Contributor

🚀 Deployed to production by https://github.com/AndrewGable in version: 9.0.40-6 🚀

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

@rayane-djouah
Copy link
Contributor

FYI, We should remove the magnifying glass button from the report header when the report is opened in the RHP. Issue: #50963

@@ -85,6 +85,7 @@ function AddressPage({title, address, updateAddress, isLoadingApp = true, backTo
title={title}
shouldShowBackButton
onBackButtonPress={() => Navigation.goBack(backTo)}
shouldDisplaySearchRouter
Copy link
Contributor

Choose a reason for hiding this comment

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

FYI, This caused this issue: #51009

@@ -261,6 +263,7 @@ function HeaderWithBackButton({
</PressableWithoutFeedback>
</Tooltip>
)}
{shouldDisplaySearchRouter && <SearchButton />}
Copy link
Contributor

Choose a reason for hiding this comment

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

FYI, This caused this issue: #51077

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.

6 participants