Skip to content

Add selection to table on MoneyRequestReport page #59433

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

jnowakow
Copy link
Contributor

@jnowakow jnowakow commented Apr 1, 2025

@Kicu @mountiny

Explanation of Change

Follow up to new MoneyRequestReport page. It adds selection to transactions table. The implementation lack support for long press selection on mobile devices, it will be added in next follow up in order to keep PRs small.

Fixed Issues

$ #57508
$ #59459
PROPOSAL: N/A

Tests

Selection doesn't work on small screen. It will be fixed in separate PR.

  1. Go to new report view -> /search/r/report-id
  2. Verify that transactions in table can be selected
  3. Verify that when any transaction is selected there is x selected button with dropdown in header
  • Verify that no errors appear in the JS console

Offline tests

  1. Go to new report view -> /search/r/report-id
  2. Verify that transactions in table can be selected
  3. Verify that when any transaction is selected there is x selected button with dropdown in header

QA Steps

Selection doesn't work on small screen. It will be fixed in separate PR.

  1. Go to new report view -> /search/r/report-id
  2. Verify that transactions in table can be selected
  3. Verify that when any transaction is selected there is x selected button with dropdown in header
  • Verify that no errors appear in the JS console

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 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 used JaimeGPT to get English > Spanish translation. I then posted it 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.ts 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.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user 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.

Screenshots/Videos

Android: Native

image

Android: mWeb Chrome

image

iOS: Native
iOS: mWeb Safari image
MacOS: Chrome / Safari
MacOS: Desktop image

@jnowakow jnowakow requested review from a team as code owners April 1, 2025 10:32
@melvin-bot melvin-bot bot requested review from DylanDylann and removed request for a team April 1, 2025 10:32
Copy link

melvin-bot bot commented Apr 1, 2025

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

@jnowakow jnowakow marked this pull request as draft April 1, 2025 10:34
@mountiny mountiny self-requested a review April 1, 2025 10:38
@jnowakow jnowakow marked this pull request as ready for review April 1, 2025 14:46
Copy link
Contributor

github-actions bot commented Apr 1, 2025

🚧 @mountiny has triggered a test app build. You can view the workflow run here.

@allgandalf
Copy link
Contributor

@jnowakow please add test steps

This comment has been minimized.

Copy link
Contributor

@allgandalf allgandalf left a comment

Choose a reason for hiding this comment

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

Code is almost ready, please update the comments and we should be good with testing this PR

Comment on lines +53 to +56
useEffect(() => {
clearErrors(ONYXKEYS.FORMS.MONEY_REQUEST_HOLD_FORM);
clearErrorFields(ONYXKEYS.FORMS.MONEY_REQUEST_HOLD_FORM);
}, []);
Copy link
Contributor

Choose a reason for hiding this comment

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

won't there be any other dependency to clear this error?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We want to clear them only when leaving page that page. It's handled that way on HoldReasonPage as well.

@shawnborton
Copy link
Contributor

I think the gap between checkbox and receipt icon is too large:
CleanShot 2025-04-01 at 21 04 50@2x

This is what the reports page looks like for reference:
CleanShot 2025-04-01 at 21 05 23@2x

Is there any way to harmonize styles between these components? My fear is that we need to maintain two separate row components that basically need to look exactly the same.

@shawnborton
Copy link
Contributor

The gaps between rows is now too large:
CleanShot 2025-04-01 at 21 06 05@2x

From staging, I see this which is correct:
CleanShot 2025-04-01 at 21 06 38@2x

@shawnborton
Copy link
Contributor

The table header is too close to the top of the view as well:
CleanShot 2025-04-01 at 21 06 59@2x

When is the last time we merged in main? Maybe these changes are available and we just need to merge them in?

Copy link
Contributor

github-actions bot commented Apr 7, 2025

🚧 @shawnborton has triggered a test app build. You can view the workflow run here.

Copy link
Contributor

github-actions bot commented Apr 7, 2025

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

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

👀 View the workflow run that generated this build 👀

@shawnborton
Copy link
Contributor

Hmm looks like we're still off by 2px:
CleanShot 2025-04-07 at 17 52 42@2x

The report itself has more padding than the reports page. Any idea what's going on?

luacmartins
luacmartins previously approved these changes Apr 7, 2025
mountiny
mountiny previously approved these changes Apr 7, 2025
Copy link
Contributor

@mountiny mountiny left a comment

Choose a reason for hiding this comment

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

Tests well for me and changes look good to me, but I would still wait for the design feedback from @shawnborton to be addressed unless he is happy to move on. This PR does hold some other changes so unless its some biggest design issues, I would recommend merging 🙌

image

@shawnborton
Copy link
Contributor

Looking good outside of my comment above about the header being slightly off, and only other comment is that if something is selected, it should not have any :hover styles - it should just keep the selectedBG color on hover.

CleanShot.2025-04-07.at.18.32.09.mp4

@jnowakow jnowakow dismissed stale reviews from mountiny and luacmartins via 8e629ce April 7, 2025 16:34
@jnowakow
Copy link
Contributor Author

jnowakow commented Apr 7, 2025

This feature is actively worked on so I would said it's good to merge this PR and fix those two UI issues in one of coming PRs

Copy link
Contributor

@mountiny mountiny left a comment

Choose a reason for hiding this comment

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

Those seem like minor checks, since we are super close to another deploy, I would merge it now and add those 2 remarks to a follow up tracker

@shawnborton
Copy link
Contributor

Fine by me!

@mountiny
Copy link
Contributor

mountiny commented Apr 7, 2025

@shawnborton thank you! Added them here in case you could just add a bit more detail so its easier for folks to squash quickly 🚀 #59452 (comment) thank you!

@mountiny mountiny merged commit e0d1735 into Expensify:main Apr 7, 2025
19 checks passed
@OSBotify
Copy link
Contributor

OSBotify commented Apr 7, 2025

✋ 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

github-actions bot commented Apr 7, 2025

🚀 Deployed to staging by https://github.com/mountiny in version: 9.1.24-2 🚀

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

Copy link
Contributor

github-actions bot commented Apr 9, 2025

🚀 Deployed to production by https://github.com/jasperhuangg in version: 9.1.24-10 🚀

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

Copy link
Contributor

github-actions bot commented Apr 9, 2025

🚀 Deployed to production by https://github.com/jasperhuangg in version: 9.1.24-10 🚀

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

@jnowakow
Copy link
Contributor Author

@shawnborton I've wanted to create follow up and add selection to mobile but I can't find designs. It should look like this:
image
but with checkboxes on items? Or like on the reports page it should go into selection mode and Report header should be replaced with something like this:
image

@shawnborton
Copy link
Contributor

Or like on the reports page it should go into selection mode and Report header should be replaced with something like this:

I think it makes sense to follow what we have for the reports page, where the whole header is replaced when we enter into select mode. cc @Expensify/design for the gut check there though!

@shawnborton
Copy link
Contributor

And yes, we need to add the checkboxes to the mobile expense rows. Again, use the Reports page as your guiding light!

@dannymcclain
Copy link
Contributor

Agree with Shawn above!

const anyTransactionOnHold = selectedTransactions.some(isOnHoldTransactionUtils);
const allTransactionOnHold = selectedTransactions.every(isOnHoldTransactionUtils);

if (!anyTransactionOnHold && selectedTransactions.length === 1) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Why was not the hold option shown when bulk selecting? Adding this line caused #60111

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I can't find conversation on slack because it was discussed in long thread but it was agreed that we don't want to iterate over selected issues and send many requests. The go to solution was to temporarily disable that option if many transactions are selected and add it when there's api to hold many transaction in one request.

Copy link
Contributor

Choose a reason for hiding this comment

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

We have a BulkHoldRequest API in place, so we can remove this limitation and start working on a fix for that.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@luacmartins great! Is there issue for it? I can replace it

Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think we have an issue yet, but I think @Tony-MK might be working on that

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.

10 participants