Skip to content

refactor: Remove shouldHandleNavigation from requestMoney and trackExpense#88055

Open
TaduJR wants to merge 13 commits intoExpensify:mainfrom
TaduJR:refactor-code-to-keep-navigation-handling-in-the-UI-components
Open

refactor: Remove shouldHandleNavigation from requestMoney and trackExpense#88055
TaduJR wants to merge 13 commits intoExpensify:mainfrom
TaduJR:refactor-code-to-keep-navigation-handling-in-the-UI-components

Conversation

@TaduJR
Copy link
Copy Markdown
Contributor

@TaduJR TaduJR commented Apr 16, 2026

Explanation of Change

Explanation of Change

PR 3 of #84631 extends the PR 2 (#86619) pattern to the two largest remaining action functions, moving navigation and draft cleanup out of requestMoney and trackExpense into their UI callers, and introducing a canonical post-creation helper that PRs 4–5 will reuse.

New helper:

  • src/libs/Navigation/helpers/cleanupAndNavigateAfterExpenseCreate.ts — wraps deferred draft cleanup, optional linked-track-report popping, activeReportID resolution, and delegation to navigateAfterExpenseCreate. Lives alongside its sibling helpers; per the architectural constraint, never invoked from src/libs/actions/.

Action layer:

  • Removed shouldHandleNavigation, backToReport, draftTransactionIDs from requestMoney and trackExpense (and from RequestMoneyInformation / CreateTrackExpenseParams types). Removed the gated removeDraftTransactionsByIDs + Navigation.removeScreenByKey blocks and the handleNavigateAfterExpenseCreate calls from both functions.
  • MoneyRequest.ts::createTransaction, handleMoneyRequestStepScanParticipants, and handleMoneyRequestStepDistanceNavigation now accept an onTransactionsCreated?: (lastTransactionID) => void callback that UI threads through to invoke cleanup + navigation in the right place.
  • Duplicate.ts (duplicateExpenseTransaction, duplicateReport, bulkDuplicateExpenses) no longer passes the removed params.
  • MoneyReportHeader.tsx, MoneyRequestHeaderSecondaryActions.tsx, useBulkDuplicateAction.ts — drop the now-unused draftTransactionIDs field from their call sites.

UI layer (calls cleanupAndNavigateAfterExpenseCreate after the action):

  • IOURequestStepConfirmation.tsx (requestMoney + trackExpense batch loops), IOURequestStepAmount.tsx, SubmitDetailsPage.tsx.
  • useReceiptScan.ts provides the onTransactionsCreated callback for the scan flow (handles the multi-receipt batch + GPS-granted / GPS-denied / no-location paths).
  • 5 distance UI files (IOURequestStepDistance.tsx, IOURequestStepDistanceMap.tsx, IOURequestStepDistanceManual.tsx, IOURequestStepDistanceOdometer.tsx, IOURequestStepDistanceGPS/index.native.tsx) provide the callback for the TRACK skip-confirm distance flow.
  • SubmitDetailsPage.tsx and IOURequestStepAmount.tsx pre-resolve and pass optimisticChatReportID so the action and post-action navigation agree on the destination if report hasn't hydrated from Onyx yet (closes codex P2).

Tests:

  • MoneyRequestTest.ts: 11 new contract tests for onTransactionsCreated — fires once per batch (not per file), AFTER all action calls, with the last file's transactionID; covers GPS-granted, GPS-denied, no-location, and early-return paths in handleMoneyRequestStepScanParticipants; covers the TRACK skip-confirm and early-return paths in handleMoneyRequestStepDistanceNavigation; undefined-callback safe.
  • 11 other test files: removed obsolete shouldHandleNavigation / backToReport / draftTransactionIDs assertions from action call fixtures (IOUTest.ts, DeleteMoneyRequestTest.ts, DuplicateTest.ts, PayMoneyRequestTest.ts, ReportWorkflowTest.ts, SplitTest.ts, TrackExpenseTest.ts, IOURequestStepAmountDraftTest.tsx, TimeExpenseConfirmationTest.tsx, UnreadIndicatorsTest.tsx, GoogleTagManagerTest.tsx).
  • 3 UI tests (IOURequestStepConfirmationPageTest.tsx, TimeExpenseConfirmationTest.tsx, MoneyRequestTest.ts): extended Navigation mocks (getReportRouteByID, removeScreenByKey, getTopmostReportId, etc.) so cleanupAndNavigateAfterExpenseCreate works in tests.

Fixed Issues

$ #84631
PROPOSAL: #84631 (comment)

Tests

  • Verify that no errors appear in the JS console

Offline tests

Same as tests

QA Steps

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

  • 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.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

@TaduJR TaduJR requested review from a team as code owners April 16, 2026 07:30
@melvin-bot melvin-bot bot requested review from joekaufmanexpensify and linhvovan29546 and removed request for a team and joekaufmanexpensify April 16, 2026 07:30
@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Apr 16, 2026

@linhvovan29546 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 removed the request for review from a team April 16, 2026 07:30
Comment thread src/pages/Share/SubmitDetailsPage.tsx Outdated
Comment thread src/pages/iou/request/step/IOURequestStepAmount.tsx
Comment thread src/pages/iou/request/step/IOURequestStepConfirmation.tsx Outdated
Comment thread src/pages/iou/request/step/IOURequestStepConfirmation.tsx Outdated
Comment thread src/pages/iou/request/step/IOURequestStepScan/hooks/useReceiptScan.ts Outdated
Comment thread src/pages/iou/request/step/IOURequestStepConfirmation.tsx Outdated
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: a063caf466

ℹ️ 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/libs/actions/IOU/TrackExpense.ts
Comment thread src/pages/iou/request/step/IOURequestStepScan/hooks/useReceiptScan.ts Outdated
TaduJR added 4 commits April 16, 2026 11:40
…de-to-keep-navigation-handling-in-the-UI-components
…de-to-keep-navigation-handling-in-the-UI-components

# Conflicts:
#	src/hooks/useExpenseActions.ts
#	src/pages/iou/request/step/IOURequestStepAmount.tsx
#	src/pages/iou/request/step/IOURequestStepConfirmation.tsx
#	tests/ui/components/IOURequestStepConfirmationPageTest.tsx
@codecov
Copy link
Copy Markdown

codecov bot commented Apr 16, 2026

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/components/MoneyReportHeader.tsx 0.00% <ø> (ø)
.../components/MoneyRequestHeaderSecondaryActions.tsx 1.04% <ø> (+0.01%) ⬆️
src/hooks/useBulkDuplicateAction.ts 100.00% <ø> (ø)
src/libs/actions/IOU/Duplicate.ts 88.03% <ø> (ø)
src/libs/actions/IOU/MoneyRequest.ts 90.81% <100.00%> (ø)
src/libs/actions/IOU/TrackExpense.ts 80.28% <100.00%> (+0.04%) ⬆️
src/libs/actions/IOU/index.ts 80.25% <ø> (ø)
...rc/pages/iou/request/step/IOURequestStepAmount.tsx 66.33% <66.66%> (+1.33%) ⬆️
...st/step/IOURequestStepDistanceGPS/index.native.tsx 0.00% <0.00%> (ø)
.../iou/request/step/IOURequestStepDistanceManual.tsx 0.00% <0.00%> (ø)
... and 7 more
... and 15 files with indirect coverage changes

TaduJR added 7 commits April 16, 2026 23:22
…de-to-keep-navigation-handling-in-the-UI-components

# Conflicts:
#	Mobile-Expensify
#	android/app/build.gradle
#	ios/NewExpensify/Info.plist
#	ios/NotificationServiceExtension/Info.plist
#	ios/ShareViewController/Info.plist
#	package-lock.json
#	package.json
#	src/pages/iou/request/step/IOURequestStepAmount.tsx
#	src/pages/iou/request/step/IOURequestStepConfirmation.tsx
#	src/stories/Form.stories.tsx
…de-to-keep-navigation-handling-in-the-UI-components
@TaduJR
Copy link
Copy Markdown
Contributor Author

TaduJR commented Apr 17, 2026

@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: 924d702b30

ℹ️ 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/pages/Share/SubmitDetailsPage.tsx
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.

1 participant