[CP Staging] fix all checkbox is auto checked when only having empty report #62111

nkdengineer · 2025-05-15T15:00:14Z

Explanation of Change

fix all checkbox is auto checked when only having empty report

Fixed Issues

$ #62086
PROPOSAL: #62086 (comment)

Tests

Precondition: The account has no expense

Create a workspace
Go FAB > Create report
Go Reports > Expense reports
Verify that the all checkbox isn't checked and it's disabled.

Verify that no errors appear in the JS console

Offline tests

None

QA Steps

Create a workspace
Go FAB > Create report
Go Reports > Expense reports
Verify that the all checkbox isn't checked and it's disabled.

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Screen.Recording.2025-05-15.at.22.01.00.mov

Android: mWeb Chrome

Screen.Recording.2025-05-15.at.21.55.27.mov

iOS: Native

Screen.Recording.2025-05-15.at.21.57.12.mov

iOS: mWeb Safari

Screen.Recording.2025-05-15.at.21.56.11.mov

MacOS: Chrome / Safari

Screen.Recording.2025-05-15.at.21.54.07.mov

MacOS: Desktop

Screen.Recording.2025-05-15.at.22.00.36.mov

melvin-bot · 2025-05-15T15:04:10Z

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

allroundexperts · 2025-05-15T15:05:27Z

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 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: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- 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 there are no new alerts related to the canBeMissing param for useOnyx
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
- 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.
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: HybridApp

Unable to build android

Android: mWeb Chrome

Screen.Recording.2025-05-15.at.8.47.05.PM.mov

iOS: HybridApp

Screen.Recording.2025-05-15.at.8.45.09.PM.mov

iOS: mWeb Safari

Screen.Recording.2025-05-15.at.8.21.28.PM.mov

MacOS: Chrome / Safari

Screen.Recording.2025-05-15.at.8.15.11.PM.mov

MacOS: Desktop

Screen.Recording.2025-05-15.at.8.17.27.PM.mov

mountiny · 2025-05-15T15:10:37Z

src/components/Search/SearchList.tsx

                            isIndeterminate={selectedItemsLength > 0 && selectedItemsLength !== flattenedTransactions.length}
                            onPress={() => {
                                onAllCheckboxPress();
                            }}
+                            disabled={flattenedTransactions.length === 0}


can you still toggle it to select that empty report?

@mountiny The checkbox of the empty report is also disabled so I think we should disabled this as well.

github-actions · 2025-05-15T15:10:50Z

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

github-actions · 2025-05-15T15:14:47Z

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

Android 🤖	iOS 🍎
Android 🤖🔄	iOS 🍎🔄


Desktop 💻	Web 🕸️
❌ FAILED ❌	https://62111.pr-testing.expensify.com
The QR code can't be generated, because the Desktop build failed

👀 View the workflow run that generated this build 👀

allroundexperts · 2025-05-15T15:22:03Z

@mountiny @nkdengineer Is this expected?

Screen.Recording.2025-05-15.at.8.21.28.PM.mov

nkdengineer · 2025-05-15T15:31:42Z

@mountiny Do you think we can also disable long press here.

mountiny · 2025-05-15T15:36:46Z

@nkdengineer we are already disabling it elsewhere

nkdengineer · 2025-05-15T15:38:07Z

@mountiny We only disable the checkbox for empty report but missed to disable the long press.

App/src/components/SelectionList/Search/ReportListItem.tsx

Lines 39 to 40 in d4347a6

    
           const isEmptyReport = reportItem.transactions.length === 0; 
        
           const isDisabledOrEmpty = isEmptyReport || isDisabled;

mountiny · 2025-05-15T15:38:31Z

#62095

nkdengineer · 2025-05-15T15:39:02Z

@mountiny We can use the same condition to return early here, what do you think?

App/src/components/Search/SearchList.tsx

Lines 176 to 178 in d4347a6

    
           if (shouldPreventLongPressRow || !isSmallScreenWidth || item?.isDisabled || item?.isDisabledCheckbox || !isFocused) { 
        
               return; 
        
           }

nkdengineer · 2025-05-15T15:39:54Z

@mountiny Thanks, we can skip this now. @allroundexperts we're good to go now.

allroundexperts

Works good!

francoisl · 2025-05-15T17:01:54Z

Cool so this is ready to go, right?

[CP Staging] fix all checkbox is auto checked when only having empty report (cherry picked from commit 7595f0f) (cherry-picked to staging by francoisl)

OSBotify · 2025-05-15T17:11:20Z

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

github-actions · 2025-05-15T17:50:45Z

🚀 Cherry-picked to staging by https://github.com/francoisl in version: 9.1.45-20 🚀

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

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

github-actions · 2025-05-15T19:04:22Z

🚀 Deployed to production by https://github.com/francoisl in version: 9.1.45-21 🚀

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

fix all checkbox is auto checked when only having empty report

f2a0023

nkdengineer marked this pull request as ready for review May 15, 2025 15:04

nkdengineer requested a review from a team as a code owner May 15, 2025 15:04

melvin-bot bot requested review from allroundexperts and removed request for a team May 15, 2025 15:04

mountiny changed the title ~~fix all checkbox is auto checked when only having empty report~~ [CP Staging] fix all checkbox is auto checked when only having empty report May 15, 2025

mountiny assigned nkdengineer May 15, 2025

mountiny reviewed May 15, 2025

View reviewed changes

allroundexperts approved these changes May 15, 2025

View reviewed changes

melvin-bot bot requested a review from mountiny May 15, 2025 15:50

francoisl approved these changes May 15, 2025

View reviewed changes

mountiny approved these changes May 15, 2025

View reviewed changes

mountiny merged commit 7595f0f into Expensify:main May 15, 2025
20 of 22 checks passed

OSBotify pushed a commit that referenced this pull request May 15, 2025

Merge pull request #62111 from nkdengineer/fix/62086

0828ecd

[CP Staging] fix all checkbox is auto checked when only having empty report (cherry picked from commit 7595f0f) (cherry-picked to staging by francoisl)

OSBotify added the CP Staging marks PRs that have been CP'd to staging label May 15, 2025

github-actions bot mentioned this pull request May 15, 2025

Deploy Checklist: New Expensify 2025-05-13 #61917

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[CP Staging] fix all checkbox is auto checked when only having empty report #62111

[CP Staging] fix all checkbox is auto checked when only having empty report #62111

nkdengineer commented May 15, 2025 •

edited

Loading

melvin-bot bot commented May 15, 2025

allroundexperts commented May 15, 2025 •

edited

Loading

mountiny May 15, 2025

nkdengineer May 15, 2025

github-actions bot commented May 15, 2025

github-actions bot commented May 15, 2025

allroundexperts commented May 15, 2025

nkdengineer commented May 15, 2025

mountiny commented May 15, 2025

nkdengineer commented May 15, 2025

mountiny commented May 15, 2025

nkdengineer commented May 15, 2025

nkdengineer commented May 15, 2025

allroundexperts left a comment

francoisl commented May 15, 2025

OSBotify commented May 15, 2025

github-actions bot commented May 15, 2025

github-actions bot commented May 15, 2025

[CP Staging] fix all checkbox is auto checked when only having empty report #62111

[CP Staging] fix all checkbox is auto checked when only having empty report #62111

Conversation

nkdengineer commented May 15, 2025 • edited Loading

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented May 15, 2025

allroundexperts commented May 15, 2025 • edited Loading

Reviewer Checklist

Screenshots/Videos

mountiny May 15, 2025

Choose a reason for hiding this comment

nkdengineer May 15, 2025

Choose a reason for hiding this comment

github-actions bot commented May 15, 2025

github-actions bot commented May 15, 2025

allroundexperts commented May 15, 2025

nkdengineer commented May 15, 2025

mountiny commented May 15, 2025

nkdengineer commented May 15, 2025

mountiny commented May 15, 2025

nkdengineer commented May 15, 2025

nkdengineer commented May 15, 2025

allroundexperts left a comment

Choose a reason for hiding this comment

francoisl commented May 15, 2025

OSBotify commented May 15, 2025

github-actions bot commented May 15, 2025

github-actions bot commented May 15, 2025

nkdengineer commented May 15, 2025 •

edited

Loading

allroundexperts commented May 15, 2025 •

edited

Loading