Skip to content

Deprecate PayMoneyRequestOnSearch in favor of individual pay commands per report#92297

Open
luacmartins wants to merge 15 commits into
mainfrom
luacmartins-pay-money-request-on-search-one-at-a-time
Open

Deprecate PayMoneyRequestOnSearch in favor of individual pay commands per report#92297
luacmartins wants to merge 15 commits into
mainfrom
luacmartins-pay-money-request-on-search-one-at-a-time

Conversation

@luacmartins
Copy link
Copy Markdown
Contributor

@luacmartins luacmartins commented Jun 1, 2026

Explanation of Change

Removes PayMoneyRequestOnSearch in favor of looping over the requests and firing individual PayMoneyRequest commands

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/643487

Tests

Pre-condition: account with several reports ready for payment

  1. Navigate to Spend
  2. Select the reports ready for payment
  3. Pay the reports
  4. Verify that it works.

Offline tests

N/A

QA Steps

Same as 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
  • 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
    • 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 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

Screen.Recording.2026-06-02.at.2.30.19.PM.mov
Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

Instead of batching all selected reports into a single
payMoneyRequestOnSearch call, send one call per report to match the
pattern used by Delete, Hold, and Unhold bulk actions.
@luacmartins luacmartins requested review from a team as code owners June 1, 2026 23:16
@melvin-bot melvin-bot Bot requested review from daledah and removed request for a team June 1, 2026 23:16
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Jun 1, 2026

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

@melvin-bot melvin-bot Bot requested review from JmillsExpensify and removed request for a team June 1, 2026 23:16
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c200ef0957

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/hooks/useSearchBulkActions.ts Outdated
@luacmartins luacmartins marked this pull request as draft June 1, 2026 23:19
@luacmartins
Copy link
Copy Markdown
Contributor Author

This is not ready for review yet.

@codecov
Copy link
Copy Markdown

codecov Bot commented Jun 1, 2026

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 Δ
...earch/SearchList/ListItem/ReportListItemHeader.tsx 91.04% <100.00%> (+1.57%) ⬆️
src/libs/API/types.ts 100.00% <ø> (ø)
.../SearchList/ListItem/TransactionListItem/index.tsx 0.00% <0.00%> (ø)
src/libs/actions/IOU/PayMoneyRequest.ts 79.41% <46.66%> (-1.94%) ⬇️
...arch/SearchList/ListItem/ExpenseReportListItem.tsx 0.00% <0.00%> (ø)
...h/SearchList/ListItem/ActionCell/PayActionCell.tsx 0.00% <0.00%> (ø)
src/libs/actions/Search.ts 34.08% <0.00%> (-1.38%) ⬇️
src/hooks/useSearchBulkActions.ts 43.69% <12.28%> (-1.84%) ⬇️
... and 11 files with indirect coverage changes

…dard pay commands

Removes the orchestrator pattern. payFromSearch routes each report to PayMoneyRequest, PayMoneyRequestWithWallet, or PayInvoice directly using API.write, which allows Auth to handle Onyx updates via queued updates. Also updates PayActionCell to use the new function.
Replaces payMoneyRequestOnSearch with payFromSearch, passing chatReportID looked up from allReports and invoice params where applicable.
Removes SIDE_EFFECT_REQUEST_COMMANDS.PAY_MONEY_REQUEST_ON_SEARCH, its params type mapping, the params file, and updates PayActionCell to use payFromSearch.
@luacmartins luacmartins changed the title PayMoneyRequestOnSearch: send one request per report from the App PayMoneyRequestOnSearch: deprecate in favor of individual pay commands per report Jun 1, 2026
@daledah
Copy link
Copy Markdown
Contributor

daledah commented Jun 2, 2026

Please let me know if the PR is ready for review 🙏

@luacmartins
Copy link
Copy Markdown
Contributor Author

@daledah not yet

@luacmartins luacmartins changed the title PayMoneyRequestOnSearch: deprecate in favor of individual pay commands per report Deprecate PayMoneyRequestOnSearch in favor of individual pay commands per report Jun 2, 2026
@luacmartins
Copy link
Copy Markdown
Contributor Author

@codex review

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a3dfb02605

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/hooks/useSearchBulkActions.ts Outdated
@luacmartins
Copy link
Copy Markdown
Contributor Author

@codex review

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 507575f680

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/hooks/useSearchBulkActions.ts Outdated
Comment thread src/libs/actions/Search.ts Outdated
@luacmartins
Copy link
Copy Markdown
Contributor Author

@codex review

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 75d8603227

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@luacmartins luacmartins marked this pull request as ready for review June 2, 2026 22:48
@luacmartins
Copy link
Copy Markdown
Contributor Author

@daledah this is ready for review

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 75d8603227

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/hooks/useSearchBulkActions.ts
Copy link
Copy Markdown
Contributor

@JmillsExpensify JmillsExpensify left a comment

Choose a reason for hiding this comment

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

My review isn't necessary here.

Comment thread src/libs/actions/IOU/PayMoneyRequest.ts Outdated
Comment thread src/hooks/useSearchBulkActions.ts Outdated
Comment thread src/hooks/useSearchBulkActions.ts Outdated
@luacmartins luacmartins requested a review from daledah June 5, 2026 16:31
@luacmartins
Copy link
Copy Markdown
Contributor Author

@daledah ready for another round

const {login: currentUserLogin, accountID: currentUserAccountID} = useCurrentUserPersonalDetails();
const {login: currentUserLogin, accountID: currentUserAccountID, email, localCurrencyCode} = useCurrentUserPersonalDetails();
const lastWorkspaceNumber = useLastWorkspaceNumber();
const [nextStep] = useOnyx(`${ONYXKEYS.COLLECTION.NEXT_STEP}${reportID}`);
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.

This component fetches a large set of Onyx data purely to pass it into payInvoice / payMoneyRequest. None of these values are used for the component's own rendering, similarly to other components.

So i think we can a shared usePaymentContext hook they consume internally and use it in the components to avoid code duplication and reduce the number of renders.

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.

3 participants