Remove global Onyx reference from createDraftTransactionAndNavigateToParticipantSelector

[cretadn22]

Explanation of Change

Fixed Issues

$ #66419
PROPOSAL: #66419

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]."

1. Create an expense in a DM chat
2. Click on the actionable button
3. Verify that it functions properly

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

Screen.Recording.2026-07-30.at.02.13.43.mov

[melvin-bot]

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

[cretadn22]

@situchan The PR is ready

[MelvinBot]

Review

👍 This is a clean, correctly-scoped refactor. The global allReportActions read is removed from createDraftTransactionAndNavigateToParticipantSelector and replaced with an explicit reportActions parameter, and every call site was updated to pass actions consistent with the reportID they already pass. No behavior change, better testability.

Verified:

• All call sites updated — both ChatActionableButtons presses (via the shared baseDraftTransactionParams) and all five DynamicReportDetailsPage sites. No other callers exist.
• Callers pass the matching data. In ChatActionableButtons the new subscription keys off actionOwnerReportID (originalReportID ?? reportID), which is exactly the reportID passed in — so it fetches the same actions the old global lookup would have. Same for actionReportID/actionReportActions in DynamicReportDetailsPage.
• Dependency arrays are correct. getOriginalReportID is hoisted out of the menuItems memo to the top level, and the memo's deps correctly swap parentReportAction, reportActionsForOriginalReportID → actionReportID, actionReportActions. Neither removed dep is referenced anywhere else inside that memo body, so no stale closure is introduced.
• Removed dead code is safe. The old if (!reportActions) return; guard was unreachable because the assignment used ?? []; the new Object.values(reportActions ?? {}) yields the same empty-iteration result when actions are missing.
• Good test coverage — the three new tests cover the found-link case, the passed-actions-take-priority-over-Onyx case, and the undefined case.

Notes (non-blocking)

• allReportActions is still read by ~13 other spots in ReportUtils.ts, so the module-level subscription rightly stays — this PR is one incremental step toward removing the global, matching its title.
• actionReportID now recomputes on every render of DynamicReportDetailsPage rather than only inside the track-expense branch. It's a cheap call returning a primitive string, so memo stability is unaffected — negligible.

No changes requested. LGTM pending the usual CI/typecheck.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. 👍

Reviewed commit: 95119c1bbf

ℹ️ 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".

[MelvinBot]

Regression check

No regressions found. This refactor is behavior-preserving — every path that previously read the global allReportActions[reportID] now receives the equivalent reportActions for the same reportID via a useOnyx subscription at the call site.

I specifically stress-tested the spots where a decoupling refactor like this usually breaks:

What I checked and why each is safe

1. Do callers pass actions for the same reportID the function keys on? Yes.

• ChatActionableButtons.tsx:62 subscribes on actionOwnerReportID (originalReportID ?? reportID) and passes reportID: actionOwnerReportID — same ID. Both button presses inherit it through the shared baseDraftTransactionParams spread.
• DynamicReportDetailsPage.tsx:219-220 subscribes on actionReportID and passes reportID: actionReportID to all three call sites — same ID.

2. The removed if (!reportActions) return; guard. Dead code, not a behavior change. The old assignment used ?? ([] as ReportAction[]), so reportActions was always a truthy array/object and the guard never fired. The new Object.values(reportActions ?? {}) produces the same empty-iteration result when actions are absent. reportActions isn't referenced anywhere else in the function body (ReportUtils.ts:11758-11760), so nothing downstream is affected.

3. undefined reportID / actionReportID edge case. getOriginalReportID returns a real ID or undefined — never an empty string — so the un-guarded useOnyx(\${...REPORT_ACTIONS}${actionReportID}`)in DynamicReportDetailsPage never collapses to a whole-collection subscription.undefinedinterpolates to the literal key...report_actions_undefined, which matches nothing → undefined→ same empty result as the oldallReportActions[...] ?? []`.

4. Memo dependency swap. The menuItems memo drops parentReportAction, reportActionsForOriginalReportID and adds actionReportID, actionReportActions. Those two removed values were only consumed inside the memo to compute actionReportID via getOriginalReportID, which is now hoisted to the top level (line 219). Neither is referenced elsewhere within the memo body, so no stale closure. actionReportID is a primitive string, so memo identity stays stable.

5. Coverage of call sites. Only two files call the function (both updated); no missed callers. reportActions is a required field on CreateDraftTransactionParams, so TypeScript would fail any construction that omitted it.

This is a static review of a pure refactor, so no production/log evidence is needed — the change adds no new runtime behavior, it only relocates where the report actions are read from. The three new unit tests already lock in the found-link, passed-over-Onyx, and undefined cases.

[situchan]

Reviewer Checklist

• I have verified the author checklist is complete (all boxes are checked off).
• I verified the correct issue is linked in the ### Fixed Issues section above
• I verified testing steps are clear and they cover the changes made in this PR
  • I verified the steps for local testing are in the Tests section
  • I verified the steps for Staging and/or Production testing are in the QA steps section
  • I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
• I included screenshots or videos for tests on all platforms
• I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
• I verified tests pass on all platforms & I tested again on:
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
• I verified proper code patterns were followed (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 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)
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I verified that this PR follows the guidelines as stated in the Review Guidelines
• I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately and each prop has a /** comment above it */
  • The file is named correctly
  • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • The only data being stored in the state is data necessary for rendering and nothing else
  • 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)
  • Any 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)
  • All JSX used for rendering exists in the render method
  • The 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
• 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 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.
• For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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 have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

android.mov

Android: mWeb Chrome

iOS: HybridApp

ios.mov

iOS: mWeb Safari

MacOS: Chrome / Safari

web.mov

[melvin-bot]

We did not find an internal engineer to review this PR, trying to assign a random engineer to #66419 as well as to this PR... Please reach out for help on Slack if no one gets assigned!