Skip to content

[BT-122] Migrate Money Request (Part 3) #83850

Closed

Description

@mjasikowski

Description

Current State:

  • 6 routes for money request destination, time, and subrate steps
  • These routes use backTo parameter for return navigation

Implementation:

  • Replace getRoute(..., backTo) with createDynamicRoute()
  • Add source screens to entryScreens array
  • Remove backTo parameter from route definitions
  • Test forward/back navigation

Scope

Routes (6):

Route Constant Path
MONEY_REQUEST_STEP_DESTINATION :action/:iouType/destination/:transactionID/:reportID
MONEY_REQUEST_STEP_DESTINATION_EDIT :action/:iouType/destination/:transactionID/:reportID/edit
MONEY_REQUEST_STEP_TIME :action/:iouType/time/:transactionID/:reportID
MONEY_REQUEST_STEP_TIME_EDIT :action/:iouType/time/:transactionID/:reportID/edit
MONEY_REQUEST_STEP_SUBRATE :action/:iouType/subrate/:transactionID/:reportID/:pageIndex
MONEY_REQUEST_STEP_SUBRATE_EDIT :action/:iouType/subrate/:transactionID/:reportID/edit/:pageIndex

Usages

MONEY_REQUEST_STEP_DESTINATION:

  • src/pages/iou/request/step/IOURequestStepDestination.tsx

MONEY_REQUEST_STEP_DESTINATION_EDIT:

  • Search for usages in destination editing flow

MONEY_REQUEST_STEP_TIME:

  • Search for usages in time selection flow

MONEY_REQUEST_STEP_TIME_EDIT:

  • Search for usages in time editing flow

MONEY_REQUEST_STEP_SUBRATE:

  • Search for usages in subrate flow

MONEY_REQUEST_STEP_SUBRATE_EDIT:

  • Search for usages in subrate editing flow

Files to modify:

  • src/ROUTES.ts - Update route definitions
  • src/libs/Navigation/types.ts - Remove backTo from params
  • Components listed above

Migration Progress

  • MONEY_REQUEST_STEP_DESTINATION
  • MONEY_REQUEST_STEP_DESTINATION_EDIT
  • MONEY_REQUEST_STEP_TIME
  • MONEY_REQUEST_STEP_TIME_EDIT
  • MONEY_REQUEST_STEP_SUBRATE
  • MONEY_REQUEST_STEP_SUBRATE_EDIT
Issue OwnerCurrent Issue Owner: @suneox

Activity

  1. added
    InternalRequires API changes or must be handled by Expensify staff
    on Mar 2, 2026
  2. huult commented on Apr 19, 2026

    @huult
    Contributor

    Not overdue

  3. 57 remaining items

  4. added a commit that references this issue on Aug 18, 2026
  5. melvin-bot commented on Aug 20, 2026

    @melvin-bot

    @suneox / @huult

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.56-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-08-27. 🎊

    The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]

  6. suneox commented on Aug 21, 2026

    @suneox
    Contributor

    the implementation plan is finished and waiting for the regression testing period

  7. melvin-bot commented on Aug 24, 2026

    @melvin-bot

    @suneox Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  8. suneox commented on Aug 26, 2026

    @suneox
    Contributor

    @mjasikowski All migrations have been deployed to production for a week, so we can close this migration

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

DailyKSv2InternalRequires API changes or must be handled by Expensify staffSkip PaymentSkips all the payment process steps for an issue. Use it for fixed-price projects.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions