Skip to content

[PR 2 of 13] Remove global Onyx reference from getOriginalReportID step 1#81707

Open
tgolen wants to merge 8 commits intomainfrom
tgolen-refactorOnyxConnection-reportactions-2and3
Open

[PR 2 of 13] Remove global Onyx reference from getOriginalReportID step 1#81707
tgolen wants to merge 8 commits intomainfrom
tgolen-refactorOnyxConnection-reportactions-2and3

Conversation

@tgolen
Copy link
Contributor

@tgolen tgolen commented Feb 6, 2026

Explanation of Change

This is the first step of several to refactor getOriginalReportID() (18 references). Here is the full refactoring plan:

  • THIS PR: Add reportActionsParam parameter and fallback to the global Onyx value for allReportActions
  • THIS PR: Update all callers to pass undefined for the parameter
  • THIS PR: Refactor 10 low-hanging fruit callers that already have reportActions available to pass that as the parameter
  • Refactor 8 difficult callers (maybe one at a time) to pass reportActions as the parameter
  • Rename reportActionsParam to reportActions
  • Remove global reference to allReportActions and the Onyx connection

Fixed Issues

Part of #66419

Tests

  1. Open a chat report with messages
  2. Tap on the "..." menu for one of the comments
  3. Tap on "Copy Link"
  4. Paste the link into a new tab and verify the report is opened and you are taken to that comment
  • Verify that no errors appear in the JS console

Offline tests

Same as tests

QA Steps

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

@codecov
Copy link

codecov bot commented Feb 6, 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 Δ
src/libs/ReportUtils.ts 74.37% <100.00%> (+0.12%) ⬆️
src/libs/actions/ReportActions.ts 78.04% <100.00%> (ø)
src/pages/ReportDetailsPage.tsx 56.28% <100.00%> (+0.11%) ⬆️
.../TransactionDuplicate/DuplicateTransactionItem.tsx 0.00% <ø> (ø)
...report/ContextMenu/BaseReportActionContextMenu.tsx 0.00% <ø> (ø)
...ort/ContextMenu/PopoverReportActionContextMenu.tsx 42.92% <100.00%> (+0.27%) ⬆️
...pages/inbox/report/ReportActionItemMessageEdit.tsx 56.00% <100.00%> (-0.70%) ⬇️
...nbox/report/ReportActionItemMessageWithExplain.tsx 85.71% <100.00%> (+2.38%) ⬆️
...ages/inbox/report/ReportActionItemParentAction.tsx 0.00% <ø> (ø)
src/pages/inbox/report/ReportActionsList.tsx 75.52% <100.00%> (+0.07%) ⬆️
... and 5 more
... and 40 files with indirect coverage changes

@tgolen tgolen changed the title Tgolen refactor onyx connection reportactions 2and3 [PR 2 of 13] Remove global Onyx reference from getOriginalReportID step 1 Feb 6, 2026
@tgolen tgolen marked this pull request as ready for review February 6, 2026 17:27
@tgolen tgolen requested review from a team as code owners February 6, 2026 17:27
@melvin-bot melvin-bot bot requested review from joekaufmanexpensify and removed request for a team February 6, 2026 17:27
@tgolen
Copy link
Contributor Author

tgolen commented Feb 6, 2026

@situchan do you want to review this one as well?

@melvin-bot melvin-bot bot requested review from carlosmiceli and removed request for a team February 6, 2026 17:27
@melvin-bot
Copy link

melvin-bot bot commented Feb 6, 2026

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

@situchan
Copy link
Contributor

situchan commented Feb 6, 2026

@situchan do you want to review this one as well?

yes thanks


function clearReportActionErrors(reportID: string, reportAction: ReportAction, keys?: string[]) {
const originalReportID = getOriginalReportID(reportID, reportAction);
const originalReportID = getOriginalReportID(reportID, reportAction, undefined);
Copy link
Contributor

Choose a reason for hiding this comment

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

❌ [PERF-2] Return early before expensive work (docs)

The function calls getOriginalReportID() before checking if reportAction?.reportActionID exists. getOriginalReportID() performs expensive operations (Onyx reads, function calls) that will be wasted if reportActionID is missing.

Fix: Move the simple validation check before the expensive work:

function clearReportActionErrors(reportID: string, reportAction: ReportAction, keys?: string[]) {
    if (!reportAction?.reportActionID) {
        return;
    }

    const originalReportID = getOriginalReportID(reportID, reportAction, undefined);
    // ... rest of function
}

Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

There is almost never a case where reportAction.reportActionID wouldn't exist, so this is not a valuable optimization.

) {
const reportID = report?.reportID;
const originalReportID = getOriginalReportID(reportID, reportAction);
const originalReportID = getOriginalReportID(reportID, reportAction, undefined);
Copy link
Contributor

Choose a reason for hiding this comment

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

❌ [PERF-2] Return early before expensive work (docs)

The function calls getOriginalReportID() (line 2095) before checking if reportAction.reportActionID exists (line 2098). getOriginalReportID() performs expensive operations (Onyx reads, function calls) that will be wasted if the validation fails.

Fix: Extract simple checks first, then perform expensive work:

const reportID = report?.reportID;
const reportActionID = reportAction.reportActionID;

if (\!reportActionID || \!reportID) {
    return;
}

const originalReportID = getOriginalReportID(reportID, reportAction, undefined);

if (\!originalReportID) {
    return;
}

Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

There is almost never a case where reportAction.reportActionID wouldn't exist, so this is not a valuable optimization.

Copy link

@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: 17ba793732

ℹ️ 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 on lines 694 to 697
const renderItem = useCallback(
({item: reportAction, index}: ListRenderItemInfo<OnyxTypes.ReportAction>) => {
const originalReportID = getOriginalReportID(report.reportID, reportAction);
const originalReportID = getOriginalReportID(report.reportID, reportAction, reportActionsFromOnyx);
const reportDraftMessages = draftMessage?.[`${ONYXKEYS.COLLECTION.REPORT_ACTIONS_DRAFTS}${originalReportID}`];

Choose a reason for hiding this comment

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

P2 Badge Recompute renderItem when reportActionsFromOnyx changes

The renderItem callback now depends on reportActionsFromOnyx to compute originalReportID, but it is not listed in the useCallback dependency array. When the report actions collection updates (e.g., Onyx loads/evicts actions after initial render), the callback will keep using a stale collection and can compute the wrong originalReportID, which then indexes drafts/emoji reactions for the wrong report. Add reportActionsFromOnyx to the dependency list (or derive originalReportID outside the callback) so it stays in sync with Onyx updates.

Useful? React with 👍 / 👎.

Comment on lines 442 to 444
if (isTrackExpenseReport && !isDeletedParentAction) {
const actionReportID = getOriginalReportID(report.reportID, parentReportAction);
const actionReportID = getOriginalReportID(report.reportID, parentReportAction, reportActionsForOriginalReportID);
const whisperAction = getTrackExpenseActionableWhisper(iouTransactionID, moneyRequestReport?.reportID);

Choose a reason for hiding this comment

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

P2 Badge Include reportActionsForOriginalReportID in menuItems deps

The menuItems useMemo now uses reportActionsForOriginalReportID when calling getOriginalReportID, but the dependency list omits reportActionsForOriginalReportID. If the report actions collection changes after initial render, the memoized actionReportID used by the Track Expense actions can become stale, leading to drafts/navigations targeting the wrong report. Include reportActionsForOriginalReportID in the dependency array so the menu recomputes when actions load or change.

Useful? React with 👍 / 👎.

@tgolen tgolen requested a review from situchan February 6, 2026 17:50
@situchan
Copy link
Contributor

situchan commented Feb 6, 2026

Copy link

@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: a351f64b3f

ℹ️ 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 on lines 476 to 482
onPress: (closePopover, {reportAction, reportActions, reportID, translate, currentUserPersonalDetails}) => {
if (!reportID) {
return;
}

const originalReportID = getOriginalReportID(reportID, reportAction);
const originalReportID = getOriginalReportID(reportID, reportAction, reportActions);
if (closePopover) {

Choose a reason for hiding this comment

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

P2 Badge Use reportActions for reportID when computing originalReportID

Here getOriginalReportID is now fed reportActions from the context menu payload, but that payload is sourced from useOnyx keyed by originalReportID (see BaseReportActionContextMenu where it loads reportActions with originalReportID). When originalReportID !== reportID (e.g., actions displayed in a different report than where they were created), the passed reportActions contains the action so getOriginalReportID returns reportID unconditionally. This causes actions like “Explain” (and also “Copy link” below) to point to the wrong report. The fix is to pass report actions for the reportID being evaluated or avoid overriding the global lookup when the payload’s actions don’t match reportID.

Useful? React with 👍 / 👎.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, that's a good call. I'll update it to get the report actions from reportID

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I actually updated this to remove getOriginalReportID() completely when I saw that originalReportID already existed in the base context.

return;
}

const originalReportID = getOriginalReportID(reportID, reportAction);
Copy link
Contributor Author

Choose a reason for hiding this comment

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

In both of these cases here, I was able to remove the call to getOriginalReportID() because the originalReportID already existed in the base context, it could be passed down directly.

return !hasCreditBankAccount(bankAccountList) ? 'bankAccount' : undefined;
}

/**
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This was 100% dead code, so easy to remove.

@situchan
Copy link
Contributor

situchan commented Feb 6, 2026

Here's the case where originalReportID and reportID is different. (one transaction report)

  1. Open workspace chat
  2. Create expense without category
  3. Click "1 Reply"
  4. Right click concierge message and copy link
  5. Verify that reportID in the copied link is originalReportID (transaction thread report), not current reportID (expense report)
Screenshot 2026-02-07 at 1 43 28 AM

@chatgpt-codex-connector
Copy link

Codex Review: Didn't find any major issues. You're on a roll.

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

@situchan
Copy link
Contributor

situchan commented Feb 6, 2026

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
    • MacOS: Desktop
  • 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 there are no new alerts related to the canBeMissing param for useOnyx
  • 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 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 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)
  • 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
  • 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.
  • 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.
  • 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: mWeb Chrome
iOS: HybridApp
ios.mov
iOS: mWeb Safari
MacOS: Chrome / Safari
web1.mov
web2.mov

Copy link
Contributor

@situchan situchan left a comment

Choose a reason for hiding this comment

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

Latest changes LGTM

@melvin-bot melvin-bot bot requested a review from lakchote February 6, 2026 20:13
@melvin-bot
Copy link

melvin-bot bot commented Feb 6, 2026

@lakchote 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
Copy link

melvin-bot bot commented Feb 6, 2026

🎯 @situchan, thanks for reviewing and testing this PR! 🎉

An E/App issue has been created to issue payment here: #81752.

@tgolen
Copy link
Contributor Author

tgolen commented Feb 6, 2026

Here's the case where originalReportID and reportID is different. (one transaction report)

Nice, looks like that's fixed in my recent changes.

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.

2 participants