Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions src/libs/Navigation/types.ts
Original file line number Diff line number Diff line change
Expand Up @@ -2035,6 +2035,8 @@ type MoneyRequestNavigatorParamList = {
transactionID: string;
reportActionID?: string;
reportID: string;
// eslint-disable-next-line no-restricted-syntax -- `backTo` usages in this file are legacy. Do not add new `backTo` params to screens. See contributingGuides/NAVIGATION.md
backTo: Routes;

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Add a runtime change for the vendor RHP glitch

In the expense-view Supplier flow I inspected, MoneyRequestView already passes getReportRHPActiveRoute() into ROUTES.MONEY_REQUEST_STEP_VENDOR.getRoute(...), and the tab-swap code in linkTo/swapBackgroundTabForRHPTarget only checks the runtime route.params.backTo. This new backTo entry is just a TypeScript param-list annotation and is erased from the bundle, so it cannot change how getMatchingFullScreenRoute sees the route or fix the reported backdrop flicker when opening the Supplier RHP.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

from Alex's Claude agent

You are right — the backTo addition is TS-only, cannot change runtime linking behavior. Closing this PR. Will reopen once I have a proper local repro to identify the actual runtime cause of the backdrop rebuild.

};
[SCREENS.MONEY_REQUEST.STEP_CATEGORY_CREATE]: {
action: IOUAction;
Expand Down
Loading