Skip to content

Pass hasReportActions to openReport (p4) - #96864

Merged
luacmartins merged 2 commits into
Expensify:mainfrom
bernhardoj:chore/73651-refactor-report-actions-to-use-useonyx-12
Jul 28, 2026
Merged

luacmartins merged 2 commits into
Expensify:mainfrom
bernhardoj:chore/73651-refactor-report-actions-to-use-useonyx-12

Conversation

@bernhardoj

Copy link
Copy Markdown
Contributor

Explanation of Change

Fixed Issues

$ #73651
PROPOSAL:

Tests

Same as QA Steps

  • Verify that no errors appear in the JS console

Offline tests

Same as QA Steps

QA Steps

A.
Prerequisite: have a workspace as admin and workspace rooms beta

  1. Open the workspace > Rooms
  2. Press any of the rooms
  3. Verify it shows the report details

B.
Prerequisite: have an expense

  1. Open an expense > Amount
  2. Copy the link
  3. Open it on an account without access to the report
  4. Verify there is no error (it'll show a not found page)

C.
Prerequisite: have a task

  1. Open the task title page
  2. Copy the link
  3. Open it on an account without access to the report
  4. Verify there is no error (it'll show a not found page)

D.
Prerequisite: have a message sent from another user

  1. Right-click the message > Flag comment
  2. Copy the link
  3. Open it on an account without access to the report
  4. Verify there is no error (it'll show a not found page)
  • 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 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 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)
  • 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.
  • 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
2.mp4
1.mp4
3.mp4
4.mp4

@bernhardoj
bernhardoj requested review from a team as code owners July 23, 2026 10:31
@melvin-bot
melvin-bot Bot requested a review from eVoloshchak July 23, 2026 10:31
@melvin-bot

melvin-bot Bot commented Jul 23, 2026

Copy link
Copy Markdown

@eVoloshchak 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 requested review from heyjennahay and removed request for a team July 23, 2026 10:31

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

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: 6f88da6584

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

selector: (reportActions) => {
return policyReports?.reduce(
(acc, curr) => {
acc[curr.reportID] = !!reportActions?.[curr.reportID];

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 Index report actions with the collection key

For admins opening Workspace > Rooms, useOnyx(ONYXKEYS.COLLECTION.REPORT_ACTIONS) returns a collection keyed by the full Onyx key, e.g. ${ONYXKEYS.COLLECTION.REPORT_ACTIONS}${reportID} as used by reportActionsExist, but this selector indexes it with the bare room ID. That makes every cached room evaluate to false, so the new openReport(..., hasReportActions: ...) call behaves as if rooms with existing actions have none and reintroduces the incorrect optimistic report update this parameter is meant to avoid.

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.

The selector returns it with the reportID as the index. Invalid review.

},
[policyID, reportNameValuePairs],
);
const [hasReportActions] = useOnyx(ONYXKEYS.COLLECTION.REPORT_ACTIONS, {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

❌ PERF-11 (docs)

This useOnyx subscribes to the entire REPORT_ACTIONS collection (one of the largest collections in the app) and its selector returns a Record<string, boolean> mapped across every policy report. Because a selector is used, Onyx runs deepEqual on this whole map on every report-action change anywhere in the app, and the selector also closes over the large external policyReports dataset and re-iterates it on each of those unrelated updates — compounding the cost. A mapped/transformed collection output like this is exactly the case PERF-11 warns against: the deepEqual is expensive and there is no meaningful re-render savings.

Instead, subscribe without a selector and build the lookup inline (or read presence per-report where it's needed), so Onyx uses the cheap shallowEqual on raw references:

const [reportActions] = useOnyx(ONYXKEYS.COLLECTION.REPORT_ACTIONS);

// where the room action is built:
const hasReportActions = !!reportActions?.[`${ONYXKEYS.COLLECTION.REPORT_ACTIONS}${report.reportID}`];
openReport({reportID: report.reportID, introSelected, betas, shouldMarkAsRead: false, hasReportActions});

This avoids the per-report mapped object and the deepEqual over the full collection.


Reviewed at: 6f88da6 | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

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.

I don't think the deepEqual will be expensive here because it's a simple boolean map.

@codecov

codecov Bot commented Jul 23, 2026 •

Copy link
Copy Markdown

Codecov Report

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

Files with missing lines Coverage Δ
src/DeepLinkHandler.tsx 86.53% <ø> (ø)
src/pages/inbox/report/withReportOrNotFound.tsx 97.36% <100.00%> (+0.07%) ⬆️
.../iou/request/step/withWritableReportOrNotFound.tsx 84.37% <100.00%> (+0.50%) ⬆️
...box/report/withReportAndReportActionOrNotFound.tsx 0.00% <0.00%> (ø)
src/pages/workspace/rooms/WorkspaceRoomsPage.tsx 0.00% <0.00%> (ø)
... and 8 files with indirect coverage changes

@eVoloshchak eVoloshchak left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

B.Prerequisite: have an expense

  1. Open an expense > Amount
  2. Copy the link
  3. Open it on an account without access to the report
  4. Verify there is no error (it'll show a not found page)

BUG

When you open a report you don't have access to (or a non-existing one) for the first time, not found page flashes multiple times. Verified this isn't present on staging

Screen.Recording.2026-07-26.at.18.15.45.mov
Screen.Recording.2026-07-26.at.18.11.11.mov

The same is true for cases C and D (a task and a message from another user)

Screen.Recording.2026-07-26.at.18.17.48.mov
Screen.Recording.2026-07-26.at.18.16.55.mov

@bernhardoj

Copy link
Copy Markdown
Contributor Author

Hmm, I can't repro it. Can you try again? I just merged with main

w.mp4

It's unlikely this PR causes that issue because hasReportActions only controls the optimistic data for reportName.

@eVoloshchak

eVoloshchak commented Jul 28, 2026 •

Copy link
Copy Markdown
Contributor

This is still reproducible, but now it's also reproducible on staging, so not related to this PR, probably related to some recent changes

@eVoloshchak

eVoloshchak commented Jul 28, 2026 •

Copy link
Copy Markdown
Contributor

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 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
    • 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
    • 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 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
screen-20260728-182531-1785255872819.mp4
Android: mWeb Chrome
Screen.Recording.2026-07-28.at.18.58.27.mov
iOS: HybridApp
Screen.Recording.2026-07-28.at.17.46.36.mov
iOS: mWeb Safari
Screen.Recording.2026-07-28.at.18.56.53.mov
MacOS: Chrome / Safari
Screen.Recording.2026-07-28.at.18.59.06.mov

@eVoloshchak eVoloshchak left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM!

@melvin-bot
melvin-bot Bot requested a review from luacmartins July 28, 2026 17:01
@luacmartins
luacmartins merged commit 2067f5d into Expensify:main Jul 28, 2026
35 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

🚧 luacmartins has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/luacmartins in version: 9.4.46-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@MelvinBot

Copy link
Copy Markdown
Contributor

I reviewed the changes in this PR and no help site changes are required under App/docs/articles.

This PR is a purely internal code refactor. It passes a new hasReportActions flag into Report.openReport(...) so the backend can skip re-fetching report actions that are already in Onyx (part of the ongoing "refactor report actions to use useOnyx" work, issue #73651).

The change is invisible to end users:

  • No new features, screens, or flows
  • No changed feature names, tab names, settings labels, or buttons
  • No behavior differences that a help article would document (the QA steps only verify existing behavior stays intact and no errors appear)

Since there's nothing user-facing to document, I did not create a draft docs PR.


@bernhardoj, since this change isn't user-facing, no help site PR was created. If you believe any of these changes do surface a documentable behavior difference, let me know and I'll draft the docs PR.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/marcaaron in version: 9.4.46-10 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Bundle Size Analysis (Sentry):

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.

5 participants