Skip to content

perf: Uplift common Onyx subscriptions from ReportActionItem to parent list components#83205

Closed
mountiny wants to merge 5 commits intomainfrom
vit-upliftCommonOnyxConnections
Closed

perf: Uplift common Onyx subscriptions from ReportActionItem to parent list components#83205
mountiny wants to merge 5 commits intomainfrom
vit-upliftCommonOnyxConnections

Conversation

@mountiny
Copy link
Contributor

@mountiny mountiny commented Feb 23, 2026

Explanation of Change

ReportActionItem is rendered once per report action inside a FlatList. Previously, each instance created its own useOnyx subscriptions for global/shared Onyx keys (e.g. CARD_LIST, BANK_ACCOUNT_LIST, NVP_INTRO_SELECTED, etc.). For a list of 50 report actions, this meant ~400-550 redundant Onyx subscriptions all returning the same data.

This PR moves 8 common Onyx subscriptions (plus 3 internal ones from the usePolicyForMovingExpenses hook) from ReportActionItem up to the parent list components (ReportActionsList and MoneyRequestReportActionsList), and passes the data as props through ReportActionsListItemRenderer and ReportActionItemParentAction.

Subscriptions uplifted:

  • ONYXKEYS.NVP_INTRO_SELECTED (was already fetched in parent lists but not passed down — duplicate removed)
  • ONYXKEYS.COLLECTION.TRANSACTION_DRAFT
  • ONYXKEYS.CARD_LIST
  • ONYXKEYS.BANK_ACCOUNT_LIST
  • ONYXKEYS.PERSONAL_POLICY_ID
  • ONYXKEYS.COLLECTION.REPORT_METADATA (was already fetched in ReportActionsList but not passed down — duplicate removed)
  • ONYXKEYS.COLLECTION.POLICY_TAGS (same key for all items since they share the same report)
  • usePolicyForMovingExpenses() hook (internally subscribes to 3 Onyx keys)

Instance-specific subscriptions that remain in ReportActionItem:

  • useOriginalReportID (depends on each action)
  • useReportIsArchived (depends on per-action originalReportID)
  • useReportTransactions (per-action iouReport)
  • linkedTransactionRouteError (per-action transactionID)

This follows the existing pattern already used for allReports, policies, personalDetails, userWalletTierName, etc.

Files changed:

  • ReportActionItem.tsx — Removed 8 useOnyx calls and the usePolicyForMovingExpenses hook; accepts the data as props instead
  • ReportActionsListItemRenderer.tsx — Added new props to type definition and passes them through to ReportActionItem and ReportActionItemParentAction
  • ReportActionItemParentAction.tsx — Added new props and passes them through to each ancestor's ReportActionItem
  • ReportActionsList.tsx — Added new useOnyx calls and usePolicyForMovingExpenses hook; passes data through renderItem
  • MoneyRequestReportActionsList.tsx — Same additions as ReportActionsList

Fixed Issues

$ #83204

Tests

  1. Open any chat report with multiple messages
  2. Verify messages render correctly with all action types (text, money requests, task previews, etc.)
  3. Click on a money request action to view the transaction thread
  4. Verify the thread parent action and its ancestors render correctly
  5. Open an expense report (money request report view)
  6. Verify all report actions render correctly in the money request list
  7. Move an expense from self-DM to a workspace (actionable track expense whisper)
  8. Verify the "Submit", "Categorize", "Share" buttons work correctly
  9. Verify modified expense messages show correct tag names
  10. Verify broken card connection messages display the correct card info
  • Verify that no errors appear in the JS console

Offline tests

  1. Go offline (disable network)
  2. Open a chat with existing messages
  3. Verify all messages still render correctly from cache
  4. Go back online
  5. Verify no errors appear and messages continue to render

QA Steps

  1. Open any chat report with several messages
  2. Verify all message types render correctly (text messages, money requests, task previews, system messages)
  3. Open an expense report and verify all actions display properly
  4. Navigate to a thread and verify ancestor actions render correctly
  5. If possible, test the "track expense" whisper flow (submit/categorize/share buttons)
  • 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

…t list components

Each ReportActionItem in a FlatList was creating its own useOnyx subscriptions
for data that is identical across all items (e.g. CARD_LIST, BANK_ACCOUNT_LIST,
NVP_INTRO_SELECTED). For a list of N items, this created N redundant
subscriptions instead of 1.

Moved 8 common subscriptions to the parent list components
(ReportActionsList, MoneyRequestReportActionsList) and pass the data
as props through ReportActionsListItemRenderer and
ReportActionItemParentAction.

Co-authored-by: Cursor <cursoragent@cursor.com>
@mountiny mountiny requested review from a team as code owners February 23, 2026 13:00
@melvin-bot melvin-bot bot requested review from joekaufmanexpensify and rojiphil and removed request for a team and joekaufmanexpensify February 23, 2026 13:00
@melvin-bot
Copy link

melvin-bot bot commented Feb 23, 2026

@rojiphil 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 removed the request for review from a team February 23, 2026 13:00
const [tryNewDot] = useOnyx(ONYXKEYS.NVP_TRY_NEW_DOT, {canBeMissing: false});
const isTryNewDotNVPDismissed = !!tryNewDot?.classicRedirect?.dismissed;
const [introSelected] = useOnyx(ONYXKEYS.NVP_INTRO_SELECTED, {canBeMissing: true});
const [allTransactionDrafts] = useOnyx(ONYXKEYS.COLLECTION.TRANSACTION_DRAFT, {canBeMissing: true});
Copy link
Contributor

Choose a reason for hiding this comment

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

❌ CONSISTENCY-3 (docs)

This block of 7 useOnyx calls and the usePolicyForMovingExpenses + policyIDForTags computation is duplicated identically in MoneyRequestReportActionsList.tsx (lines 170-177). Both list components fetch the exact same data for the exact same purpose (passing it down to ReportActionsListItemRenderer -> ReportActionItem).

Consider extracting these shared subscriptions into a custom hook, e.g.:

function useReportActionItemOnyxData(report: OnyxEntry<Report>) {
    const [allTransactionDrafts] = useOnyx(ONYXKEYS.COLLECTION.TRANSACTION_DRAFT, {canBeMissing: true});
    const [cardList] = useOnyx(ONYXKEYS.CARD_LIST, {canBeMissing: true});
    const [bankAccountList] = useOnyx(ONYXKEYS.BANK_ACCOUNT_LIST, {canBeMissing: true});
    const [personalPolicyID] = useOnyx(ONYXKEYS.PERSONAL_POLICY_ID, {canBeMissing: true});
    const {policyForMovingExpensesID} = usePolicyForMovingExpenses();
    const policyIDForTags = report?.policyID === CONST.POLICY.OWNER_EMAIL_FAKE && policyForMovingExpensesID ? policyForMovingExpensesID : report?.policyID;
    const [policyTags] = useOnyx(`${ONYXKEYS.COLLECTION.POLICY_TAGS}${policyIDForTags}`, {canBeMissing: true});

    return {allTransactionDrafts, cardList, bankAccountList, personalPolicyID, policyTags};
}

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.

I am not sure if this is going to be much cleaner in this case

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: 4bfd92ed91

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

@codecov
Copy link

codecov bot commented Feb 23, 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/pages/inbox/report/ReportActionItem.tsx 100.00% <ø> (ø)
src/pages/inbox/report/ReportActionsList.tsx 80.95% <100.00%> (+0.40%) ⬆️
...ges/inbox/report/ReportActionsListItemRenderer.tsx 85.71% <ø> (ø)
...equestReportView/MoneyRequestReportActionsList.tsx 0.66% <0.00%> (-0.02%) ⬇️
...ages/inbox/report/ReportActionItemParentAction.tsx 0.00% <0.00%> (ø)
... and 19 files with indirect coverage changes

mountiny and others added 3 commits February 23, 2026 14:30
Resolved conflicts in ReportActionItem.tsx, ReportActionsList.tsx, and
MoneyRequestReportActionsList.tsx caused by main removing canBeMissing
options from useOnyx calls. Updated our uplifted subscriptions to match.

Co-authored-by: Cursor <cursoragent@cursor.com>
ReportActionItemParentAction now subscribes to per-ancestor
reportMetadata and policyTags using collection selectors (matching the
existing pattern for ancestorsReportNameValuePairs), instead of
receiving a single shared value from the parent list. This ensures
ancestors in thread views get correct per-report metadata and
per-workspace tag labels.

Also makes personalPolicyID and allTransactionDrafts optional in
ReportActionItemProps so callers that use ReportActionItem directly
(DuplicateTransactionItem, DebugReportActionPreview,
DebugReportActionCreatePage, ChatListItem) don't need to provide them.

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@mountiny
Copy link
Contributor Author

@adhorodyski Will you be able to test out the performance here?

Co-authored-by: Cursor <cursoragent@cursor.com>
@adhorodyski
Copy link
Contributor

Yes. FYI we're looking for a good, proper way to refactor these list items without causing mass disruption, while bringing in big performance gains with @TMisiukiewicz. As much as this can even bring in small gains, I'd say it's first (and foremost?) idiomatically incorrect, because truth is not all list elements will require these properties. I'll look into it more closely on tomorrow and get back to you!

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