Skip to content

Allow rejecting expenses in bulk in NewDot#72855

Merged
luacmartins merged 27 commits intomainfrom
lucien/reject-bulk-action
Oct 29, 2025
Merged

Allow rejecting expenses in bulk in NewDot#72855
luacmartins merged 27 commits intomainfrom
lucien/reject-bulk-action

Conversation

@lakchote
Copy link
Contributor

@lakchote lakchote commented Oct 17, 2025

Explanation of Change

Allow rejecting expenses in bulk in NewDot

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/557590
PROPOSAL:

Tests

  • Verify that no errors appear in the JS console
Screen.Recording.2025-10-17.at.11.08.08.mov

Prerequisites:

  • having a workspace
  • a workspace owner
  • a submitter
  1. Create and submit two expenses as a submitter
  2. Go to the Reports page as the workspace owner, bulk select the two expenses
  3. Select Reject
  4. Provide the rejection reason
  5. Verify it succeeds, and that the rejection message is propagated to the two transaction threads

Offline tests

NA, it's the reports page

QA Steps

  • Verify that no errors appear in the JS console

Same as in tests

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.
  • I verified that similar component doesn't exist in the codebase
  • I verified that all props are defined accurately and each prop has a /** comment above it */
  • I verified that each file is named correctly
  • I verified that each component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • I verified that the only data being stored in component state is data necessary for rendering and nothing else
  • In component if we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
  • 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)
  • I verified that component 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)
  • I verified that all JSX used for rendering exists in the render method
  • I verified that each 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

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
Screen.Recording.2025-10-17.at.11.08.08.mov
MacOS: Desktop

@OSBotify
Copy link
Contributor

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 4af77e7b..806794bb 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -6221,7 +6221,7 @@ ${amount} pour ${merchant} - ${date}`,
             delete: 'Supprimer',
             hold: 'Attente',
             unhold: 'Supprimer la suspension',
-            reject: 'Rejeter',
+            reject: 'Refuser',
             noOptionsAvailable: 'Aucune option disponible pour le groupe de dépenses sélectionné.',
         },
         filtersHeader: 'Filtres',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index caac87fd..0ac72c15 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -6077,15 +6077,7 @@ ${merchant}的${amount} - ${date}`,
         searchName: '搜索名称',
         savedSearchesMenuItemTitle: '已保存',
         groupedExpenses: '分组费用',
-        bulkActions: {
-            approve: '批准',
-            pay: '支付',
-            delete: '删除',
-            hold: '保持',
-            unhold: '移除保留',
-            reject: '拒绝',
-            noOptionsAvailable: '所选费用组没有可用选项。',
-        },
+        bulkActions: {approve: '批准', pay: '支付', delete: '删除', hold: '保持', unhold: '移除保留', reject: '拒绝', noOptionsAvailable: '所选费用组没有可用选项。'},
         filtersHeader: '筛选器',
         filters: {
             date: {

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

@codecov
Copy link

codecov bot commented Oct 17, 2025

Codecov Report

❌ Patch coverage is 16.27907% with 36 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
src/pages/Search/SearchPage.tsx 0.00% 15 Missing ⚠️
src/libs/actions/Search.ts 0.00% 13 Missing ⚠️
src/pages/Search/SearchRejectReasonPage.tsx 0.00% 4 Missing ⚠️
...gation/AppNavigator/ModalStackNavigators/index.tsx 0.00% 2 Missing ⚠️
src/libs/actions/IOU.ts 87.50% 1 Missing ⚠️
src/pages/Search/SearchHoldReasonPage.tsx 0.00% 1 Missing ⚠️
Files with missing lines Coverage Δ
src/CONST/index.ts 85.71% <ø> (ø)
src/ROUTES.ts 11.11% <ø> (+0.22%) ⬆️
src/SCREENS.ts 100.00% <ø> (ø)
...avigation/linkingConfig/RELATIONS/SEARCH_TO_RHP.ts 100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts 75.00% <ø> (ø)
src/pages/iou/RejectReasonFormView.tsx 0.00% <ø> (ø)
src/libs/actions/IOU.ts 63.78% <87.50%> (+0.28%) ⬆️
src/pages/Search/SearchHoldReasonPage.tsx 0.00% <0.00%> (ø)
...gation/AppNavigator/ModalStackNavigators/index.tsx 8.30% <0.00%> (-0.06%) ⬇️
src/pages/Search/SearchRejectReasonPage.tsx 0.00% <0.00%> (ø)
... and 2 more

... and 1431 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@lakchote lakchote marked this pull request as ready for review October 20, 2025 16:09
@lakchote lakchote requested a review from a team as a code owner October 20, 2025 16:09
@melvin-bot melvin-bot bot requested review from ikevin127 and removed request for a team October 20, 2025 16:09
@melvin-bot
Copy link

melvin-bot bot commented Oct 20, 2025

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

@lakchote lakchote requested review from luacmartins and removed request for ikevin127 October 20, 2025 16:09

const validate = useCallback(
(values: FormOnyxValues<typeof ONYXKEYS.FORMS.MONEY_REQUEST_REJECT_FORM>) => {
const errors: FormInputErrors<typeof ONYXKEYS.FORMS.MONEY_REQUEST_REJECT_FORM> = getFieldRequiredErrors(values, [INPUT_IDS.COMMENT]);
Copy link
Contributor

Choose a reason for hiding this comment

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

❌ Redundant validation logic

The validation logic here is redundant. Line 36 calls getFieldRequiredErrors(values, [INPUT_IDS.COMMENT]) and then line 38 manually checks if (!values.comment) for the same field.

Fix: Remove the redundant manual check on line 38-40 since getFieldRequiredErrors already handles this:

const validate = useCallback(
    (values: FormOnyxValues<typeof ONYXKEYS.FORMS.MONEY_REQUEST_REJECT_FORM>) => {
        const errors: FormInputErrors<typeof ONYXKEYS.FORMS.MONEY_REQUEST_REJECT_FORM> = getFieldRequiredErrors(values, [INPUT_IDS.COMMENT]);
        return errors;
    },
    [translate],
);

Copy link
Contributor

Choose a reason for hiding this comment

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

This makes sense. Let's remove the manual check below

@luacmartins luacmartins requested a review from situchan October 20, 2025 17:09

const validate = useCallback(
(values: FormOnyxValues<typeof ONYXKEYS.FORMS.MONEY_REQUEST_REJECT_FORM>) => {
const errors: FormInputErrors<typeof ONYXKEYS.FORMS.MONEY_REQUEST_REJECT_FORM> = getFieldRequiredErrors(values, [INPUT_IDS.COMMENT]);
Copy link
Contributor

Choose a reason for hiding this comment

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

This makes sense. Let's remove the manual check below


/** Link to previous page */
backTo: Route;
backTo?: Route;
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This one is a pre-existing file. The deprecated aspect of the backTo parameter can be handled in a follow up by the person in charge of the FE implementation of the Reject in NewDot project. cc @mananjadhav @truph01

Copy link
Collaborator

Choose a reason for hiding this comment

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

I'll take care of it.

const errors: FormInputErrors<typeof ONYXKEYS.FORMS.MONEY_REQUEST_REJECT_FORM> = getFieldRequiredErrors(values, [INPUT_IDS.COMMENT]);
return errors;
},
[translate],
Copy link
Contributor

Choose a reason for hiding this comment

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

❌ PERF-6 (docs)

In useCallback, specify individual object properties as dependencies instead of passing the entire context object.

const onSubmit = useCallback(
    ({comment}: FormOnyxValues<typeof ONYXKEYS.FORMS.MONEY_REQUEST_REJECT_FORM>) => {
        rejectMoneyRequestsOnSearch(context.currentSearchHash, context.selectedTransactions, comment);
        context.clearSelectedTransactions();
        Navigation.goBack();
    },
    [context.currentSearchHash, context.selectedTransactions, context.clearSelectedTransactions],
);

});

Object.entries(transactionsByReport).forEach(([reportID, reportTransactionIDs]) => {
// Share a single destination ID across all rejections from the same source report
Copy link
Contributor

Choose a reason for hiding this comment

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

❌ JSDoc Comments (docs)

Missing JSDoc documentation for the rejectMoneyRequestsOnSearch function. All functions should have proper JSDoc comments explaining their purpose, parameters, and return values.

/**
 * Reject multiple money requests from search results in bulk
 * @param hash - The search query hash
 * @param selectedTransactions - Map of selected transactions with their metadata
 * @param comment - The rejection reason comment
 */
function rejectMoneyRequestsOnSearch(hash: number, selectedTransactions: SelectedTransactions, comment: string) {

import ONYXKEYS from '@src/ONYXKEYS';
import INPUT_IDS from '@src/types/form/MoneyRequestRejectReasonForm';

function SearchRejectReasonPage() {
Copy link
Contributor

Choose a reason for hiding this comment

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

❌ JSDoc Comments (docs)

Missing JSDoc documentation for the SearchRejectReasonPage component. Component functions should have proper JSDoc comments explaining their purpose.

/**
 * Page for entering a rejection reason when bulk rejecting expenses from search results
 */
function SearchRejectReasonPage() {

@lakchote
Copy link
Contributor Author

@situchan @luacmartins @stitesExpensify ready for a re-review, tests pass.

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 luacmartins merged commit 9d30cbc into main Oct 29, 2025
34 of 36 checks passed
@luacmartins luacmartins deleted the lucien/reject-bulk-action branch October 29, 2025 18:14
@OSBotify
Copy link
Contributor

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

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

@dangrous
Copy link
Contributor

@lakchote - #73817 came up when testing this; doesn't feel like a blocker, right? Just an improvement after the fact? Let me know!

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/puneetlath in version: 9.2.41-6 🚀

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

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.

9 participants