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

Hide mobile Search nav button + status tabs on scrollDown, but reveal on scrollUp #48258

Merged

Conversation

SzymczakJ
Copy link
Contributor

@SzymczakJ SzymczakJ commented Aug 29, 2024

Details

This PR adds an animation that hides mobile Search nav bar on scroll down and reveals it on scrollUp. Please note that this feature is only meant to work on mobile screens. Also when user doesn't have enough expenses, the bar won't hide.

Fixed Issues

$ #48019
PROPOSAL:

Tests

  1. Go to Search tab that has a lot of expenses.
  2. Try scrolling and make sure expense type and status bar hides and shows properly.
  3. Go to Search tab that has little or no expenses.
  4. Make sure and make sure expense type and status bar is locked in place.

Offline tests

QA Steps

Same as test steps

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
animAndroid.mov
Android: mWeb Chrome
animAndroidweb.mov
iOS: Native
animIos.mov
iOS: mWeb Safari
iosweb.mov
MacOS: Chrome / Safari Screenshot 2024-08-30 at 10 37 31
MacOS: Desktop Screenshot 2024-09-27 at 13 31 17

Copy link
Contributor

@Guccio163 Guccio163 left a comment

Choose a reason for hiding this comment

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

generally LGTM, works great! 👀

Copy link
Contributor

@Kicu Kicu left a comment

Choose a reason for hiding this comment

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

Hey very nice work both on animation and refactoring. SearchPageHeader feels much simpler, and also Search component also looks simpler.

My only real problem is with SearchPageBottom because it became harder to read.
Most of my comments are minor naming issues, LGTM otherwise 👍

src/pages/Search/SearchPageBottomTab.tsx Outdated Show resolved Hide resolved
src/components/Search/index.tsx Outdated Show resolved Hide resolved
src/components/Search/SearchStatusBar.tsx Outdated Show resolved Hide resolved
isCustomQuery: boolean;
setOfflineModalOpen?: () => void;
setDownloadErrorModalOpen?: () => void;
data?: TransactionListItemType[] | ReportListItemType[];
Copy link
Contributor

Choose a reason for hiding this comment

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

great job removing so many props! 👏

src/components/Search/index.tsx Outdated Show resolved Hide resolved
src/components/Search/index.tsx Outdated Show resolved Hide resolved
src/components/SelectionList/index.tsx Outdated Show resolved Hide resolved
src/libs/SearchUtils.ts Outdated Show resolved Hide resolved
hash={queryJSON.hash}
isCustomQuery={isCustomQuery}
/>
)}
Copy link
Contributor

Choose a reason for hiding this comment

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

Do you think its possible to somehow simplify this and reduce the amount of conditional rendering inside this return?
We have conditional rendering for TopBar + SearchTypeMenu, then extra condition for SearchStatusBar and all that is exclusive with SearchPageHeader rendering.
It's very hard to understand which parts of the UI will be rendered.

Some ideas:

  • early returns?
  • saving parts of JSX to variables?
  • small helper components declared within this file?

I think you could try to go over this code again and see if anything can be improved.

@SzymczakJ SzymczakJ marked this pull request as ready for review September 4, 2024 09:05
@SzymczakJ SzymczakJ requested review from a team as code owners September 4, 2024 09:05
@melvin-bot melvin-bot bot requested review from rayane-djouah and removed request for a team September 4, 2024 09:06
Copy link

melvin-bot bot commented Sep 4, 2024

@rayane-djouah 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]

@shawnborton
Copy link
Contributor

Running a test build for easier testing...

This comment has been minimized.

@shawnborton
Copy link
Contributor

Any idea how to fix the iOS build above so we can test?

@SzymczakJ
Copy link
Contributor Author

I merged main and the error should be solved(ruby-version file was missing, but it was reintroduced after merge). Can you try again?

@shawnborton
Copy link
Contributor

Will do!

Copy link
Contributor

github-actions bot commented Sep 4, 2024

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪

Android 🤖 iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/48258/index.html https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/48258/index.html
Android iOS
Desktop 💻 Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/48258/NewExpensify.dmg https://48258.pr-testing.expensify.com
Desktop Web

👀 View the workflow run that generated this build 👀

@dannymcclain
Copy link
Contributor

I think this is feeling pretty darn good!

@dubielzyk-expensify
Copy link
Contributor

dubielzyk-expensify commented Sep 24, 2024

Ignore me haha. I think I got the multi-select mode mixed up. My bad 😅

Agree with what Danny is saying 😄

@luacmartins
Copy link
Contributor

Cool, so it seems like the current behavior is expected. @rayane-djouah let's continue with the review.

@rayane-djouah
Copy link
Contributor

@SzymczakJ Let's address my requested changes above

@rayane-djouah
Copy link
Contributor

We have conflicts also

@luacmartins
Copy link
Contributor

Waiting on @SzymczakJ to address the comments above

@SzymczakJ
Copy link
Contributor Author

I'll work on it today, I'm just prioritising #49457

@luacmartins
Copy link
Contributor

@SzymczakJ yes, let's prioritize #49457

@SzymczakJ
Copy link
Contributor Author

Bumped into bug on #49457, so no update for today

@SzymczakJ
Copy link
Contributor Author

fixed comments and conflicts @rayane-djouah

@SzymczakJ
Copy link
Contributor Author

kind bump @rayane-djouah 🙇

Copy link
Contributor

@rayane-djouah rayane-djouah left a comment

Choose a reason for hiding this comment

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

Looks good! One last comment

@@ -45,7 +45,7 @@ function SearchSelectedNarrow({options, itemsLength}: SearchSelectedNarrowProps)
};

return (
<View style={[styles.pb4]}>
<View>
Copy link
Contributor

Choose a reason for hiding this comment

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

Last comment 😄 : To make this view consistent with the room members view, let's reduce the padding to 12px instead of removing it entirely. This way, we will have a total of 24px between the drop-down button and the 'Select All' checkbox.

Suggested change
<View>
<View style={[styles.pb3]} >
Room members Search
Screenshot 2024-09-30 at 11 02 14 AM Screenshot 2024-09-30 at 11 16 41 AM

@SzymczakJ
Copy link
Contributor Author

Done!

Copy link
Contributor

@rayane-djouah rayane-djouah left a comment

Choose a reason for hiding this comment

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

Looks good to me and tests well. Thanks for the great work!

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 great work!

@luacmartins luacmartins merged commit decf515 into Expensify:main Sep 30, 2024
17 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.

@Kicu
Copy link
Contributor

Kicu commented Sep 30, 2024

👏

Copy link
Contributor

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

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

Copy link
Contributor

github-actions bot commented Oct 2, 2024

🚀 Deployed to production by https://github.com/jasperhuangg in version: 9.0.42-3 🚀

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

@ikevin127
Copy link
Contributor

This PR caused the following issue:

which was caused by wrapping SearchTypeMenu in Animated.View which caused the scroll to stop working. It was fixed in a follow-up PR by this PRs reviewer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants