Skip to content

[WIP] fix: follow up Reject bugs for Bulk Reject#73932

Closed
lakchote wants to merge 6 commits intomainfrom
lucien/bulk-reject-fix-bugs
Closed

[WIP] fix: follow up Reject bugs for Bulk Reject#73932
lakchote wants to merge 6 commits intomainfrom
lucien/bulk-reject-fix-bugs

Conversation

@lakchote
Copy link
Copy Markdown
Contributor

@lakchote lakchote commented Oct 31, 2025

Explanation of Change

Undoes the revert of #72855.

Also fixes bugs reported by QA:

Bugs remaining:

Fixed Issues

$
PROPOSAL:

Tests

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

  • 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 verified there are no new alerts related to the canBeMissing param for useOnyx
  • 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 new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • 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
MacOS: Desktop

@lakchote lakchote self-assigned this Oct 31, 2025
@OSBotify
Copy link
Copy Markdown
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 bb3ba598..46e8d2e4 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -6280,7 +6280,7 @@ ${amount} pour ${merchant} - ${date}`,
             delete: 'Supprimer',
             hold: 'Attente',
             unhold: 'Supprimer la suspension',
-            reject: 'Refuser',
+            reject: 'Rejeter',
             noOptionsAvailable: 'Aucune option disponible pour le groupe de dépenses sélectionné.',
         },
         filtersHeader: 'Filtres',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 81201975..2f17cfe9 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -4432,7 +4432,6 @@ ${amount} dla ${merchant} - ${date}`,
             displayedAsTagDescription: 'Dział będzie można wybrać dla każdego indywidualnego wydatku w raporcie pracownika.',
             displayedAsReportFieldDescription: 'Wybór działu będzie dotyczył wszystkich wydatków w raporcie pracownika.',
             toggleImportTitle: ({mappingTitle}: ToggleImportTitleParams) => `Wybierz, jak obsługiwać Sage Intacct <strong>${mappingTitle}</strong> w Expensify.`,
-
             expenseTypes: 'Typy wydatków',
             expenseTypesDescription: 'Twoje typy wydatków Sage Intacct zostaną zaimportowane do Expensify jako kategorie.',
             accountTypesDescription: 'Twój plan kont Sage Intacct zostanie zaimportowany do Expensify jako kategorie.',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 208e8439..80b324b1 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -4431,7 +4431,6 @@ ${amount} para ${merchant} - ${date}`,
             displayedAsTagDescription: 'O departamento será selecionável para cada despesa individual no relatório de um funcionário.',
             displayedAsReportFieldDescription: 'A seleção de departamento será aplicada a todas as despesas no relatório de um funcionário.',
             toggleImportTitle: ({mappingTitle}: ToggleImportTitleParams) => `Escolha como lidar com o Sage Intacct <strong>${mappingTitle}</strong> in Expensify.`,
-
             expenseTypes: 'Tipos de despesas',
             expenseTypesDescription: 'Seus tipos de despesas do Sage Intacct serão importados para o Expensify como categorias.',
             accountTypesDescription: 'Seu plano de contas do Sage Intacct será importado para o Expensify como categorias.',
@@ -7369,7 +7368,6 @@ ${amount} para ${merchant} - ${date}`,
         exportInProgress: 'Exportação em andamento',
         conciergeWillSend: 'Concierge enviará o arquivo em breve.',
     },
-
     avatarPage: {
         title: 'Editar foto de perfil',
         upload: 'Carregar',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index a428c925..9ad4aa39 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -6130,15 +6130,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 😉

import type {SearchResults, Transaction} from '@src/types/onyx';
import type {FileObject} from '@src/types/utils/Attachment';
import SearchPageNarrow from './SearchPageNarrow';
import { getTransactionViolationsOfTransaction } from '@libs/TransactionUtils';
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code Style Issue

The import statement has improper spacing. According to the codebase conventions, there should be no spaces after the opening brace or before the closing brace.

Suggested fix:

import {getTransactionViolationsOfTransaction} from '@libs/TransactionUtils';

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

Choose a reason for hiding this comment

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

Unnecessary Dependency

The translate variable is included in the dependency array but is not used within the validate callback function. This creates an unnecessary dependency that could cause the function to be recreated when translate changes.

Suggested fix:

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;
    },
    [], // Remove translate from dependencies since it's not used
);

return {areHydrated: true, missingReportIDs: [], missingPolicyIDs: []};
}
return checkBulkRejectHydration(selectedTransactions, policies);
}, [selectedTransactions, policies]);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

❌ PERF-6 (docs)

Passing entire objects (selectedTransactions, policies) as dependencies causes this hook to re-execute whenever any property in these objects changes, even unrelated ones. This creates unnecessary computation overhead.

Suggested fix:
Extract the specific values needed and use them as dependencies:

const selectedTransactionsLength = Object.keys(selectedTransactions).length;
const bulkRejectHydrationStatus = useMemo(() => {
    if (selectedTransactionsLength === 0) {
        return {areHydrated: true, missingReportIDs: [], missingPolicyIDs: []};
    }
    return checkBulkRejectHydration(selectedTransactions, policies);
}, [selectedTransactions, policies, selectedTransactionsLength]);

Note: In this case, since checkBulkRejectHydration needs the full objects to iterate over them, you may need to keep these dependencies. However, consider if the hydration check could be performed more efficiently or if you can use more specific dependencies based on what triggers the need for re-checking.

@codecov
Copy link
Copy Markdown

codecov bot commented Oct 31, 2025

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/CONST/index.ts 85.71% <ø> (ø)
src/ROUTES.ts 11.00% <ø> (ø)
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.38% <87.50%> (-0.34%) ⬇️
src/pages/Search/SearchHoldReasonPage.tsx 0.00% <0.00%> (ø)
...gation/AppNavigator/ModalStackNavigators/index.tsx 8.30% <0.00%> (-0.03%) ⬇️
src/pages/Search/SearchRejectReasonPage.tsx 0.00% <0.00%> (ø)
... and 3 more
... and 45 files with indirect coverage changes

@lakchote lakchote mentioned this pull request Oct 31, 2025
58 tasks
@lakchote
Copy link
Copy Markdown
Contributor Author

lakchote commented Nov 3, 2025

@truph01 will take over to finish the remaining bug fixes, and @mananjadhav will then review it.

cc @trjExpensify

@garrettmknight
Copy link
Copy Markdown
Contributor

@truph01 when do you think you'll be able to get moving on this one?

@truph01
Copy link
Copy Markdown
Contributor

truph01 commented Nov 5, 2025

@garrettmknight I already have an idea for how to fix the bugs, but I'm currently stuck on checking out the branch lucien/bulk-reject-fix-bugs to continue working on it.

It seems I need the permissions to checkout.

@lakchote
Copy link
Copy Markdown
Contributor Author

lakchote commented Nov 5, 2025

I've created a fork and now @truph01 will be able to work on the PR.

@trjExpensify
Copy link
Copy Markdown
Contributor

@truph01 can you give an update on progress?

@truph01
Copy link
Copy Markdown
Contributor

truph01 commented Nov 10, 2025

@lakchote
Copy link
Copy Markdown
Contributor Author

@lakchote lakchote closed this Nov 14, 2025
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.

5 participants