Skip to content

refactor: PureReportActionItem, ReportActionItemEmojiReactions#88324

Merged
cristipaval merged 11 commits intoExpensify:mainfrom
callstack-internal:perf-send-message-phase-12
Apr 22, 2026
Merged

refactor: PureReportActionItem, ReportActionItemEmojiReactions#88324
cristipaval merged 11 commits intoExpensify:mainfrom
callstack-internal:perf-send-message-phase-12

Conversation

@LukasMod
Copy link
Copy Markdown
Contributor

@LukasMod LukasMod commented Apr 20, 2026

Explanation of Change

Emoji reactions decomposition

  • ReportActionItemEmojiReactions now owns all data it consumes. Self-subscribes to REPORT_ACTIONS_REACTIONS (via useOnyx), useCurrentUserPersonalDetails, and useLocalize. Drops the emojiReactions, currentUserAccountID, toggleEmojiReaction, and preferredLocale props.
  • Kills the full emojiReactions prop chain through PureReportActionItemReportActionItemReportActionsListItemRenderer / DuplicateTransactionItem / ReportActionItemParentAction. Removes 3 upstream useOnyx calls and one deepEqual entry from PureReportActionItem's memo comparator.
  • Replaces the emojiReactions={isOnSearch ? {} : …} "mute" with a !isOnSearch mount gate on the reactions block — matches how the sibling thread-replies block already handles Search.
  • Modernizes ReactionTooltipContent. Replaces the legacy withCurrentUserPersonalDetails HOC with useCurrentUserPersonalDetails, and moves emoji-name localization into the tooltip itself (it already uses useLocalize), so callers can pass the raw English name and stop threading preferredLocale / currentUserPersonalDetails through the list-item render path.

Language fix

emoji-name tooltips stayed blank for non-EN users until they typed in the composer, the localized emoji table is lazy-loaded inside getEmojiTrie, which is only called from the composer path (recently introduced).

Fixed by firing importEmojiLocale(preferredLocale) inside ReportActionItemEmojiReactions when a reaction row first renders with reactions. Matches the composer's on-demand pattern (no boot cost, no useEffect, no bundle regression), fires strictly on-demand (only when a user is actually in a chat with emoji reactions), and resolves well before the user has time to hover a bubble.

Fixed Issues

$ #88377
PROPOSAL:

Tests

  • Verify that no errors appear in the JS console

Test 1: Basic reactions flow:

  1. In any chat, hover over a message and add an emoji reaction, verify the bubble appears with count 1.
  2. Hover the bubble, verify the tooltip shows the correct user display name and the emoji name (e.g. 😄)
  3. Click the same bubble, verify your reaction is removed; the bubble disappears when count hits 0.
  4. React with multiple distinct emojis on one message, verify each gets its own bubble and ordering stays stable.

Test 2: Search surface:

  1. Open Search and find a message that has reactions.
  2. In the search result preview, verify reactions (and thread replies) are not rendered.
  3. Open the actual chat from search, verify the reactions reappear.

Test 3: Localization:

  1. Change app language (Settings → Preferences → Language) to Spanish,
  2. Verify the emoji name shown in the reaction tooltip is translated (before this PR this would have stayed in English or empty).
  3. Refresh page and try verify again

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

  • 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.native.mov
Android: mWeb Chrome
android.web.mov

new video:
https://github.com/user-attachments/assets/4ee2ea1d-1429-4f78-bd83-81fe8c2cca1f

iOS: Native
ios.native.mov
iOS: mWeb Safari
ios.web.mov

new video:
https://github.com/user-attachments/assets/8d4af4c2-75a9-4e8f-b2ca-8301eac0e0d9

MacOS: Chrome / Safari
web.mov

LukasMod and others added 7 commits April 21, 2026 10:31
Swap withCurrentUserPersonalDetails HOC for the useCurrentUserPersonalDetails hook.
No behavior change — both read the same Context — but removes the HOC wrapper and
aligns the component with the current codebase convention.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Drop the unused preferredLocale prop and read it from useLocalize() inside the
component. The prop was never threaded through PureReportActionItem, so the
component was silently falling back to CONST.LOCALES.DEFAULT — this change fixes
that latent bug and removes one prop from the interface.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…tions

Replace the emojiReactions prop with a direct useOnyx subscription on
REPORT_ACTIONS_REACTIONS. Use the shared getEmptyObject<ReportActionReactions>()
helper for the stable empty default (matches BaseQuickEmojiReactions /
MiniQuickEmojiReactions).

Clean up the full prop chain:
- PureReportActionItem no longer takes/forwards emojiReactions; its memo loses
  the deepEqual(emojiReactions) entry.
- The isOnSearch ? {} override is replaced with an !isOnSearch mount gate in the
  parent, so on search we skip the mount (and the subscription) entirely.
- ReportActionItem, ReportActionsListItemRenderer, DuplicateTransactionItem and
  ReportActionItemParentAction drop the prop and the now-unused useOnyx calls /
  selectors that only existed to source it.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@LukasMod LukasMod force-pushed the perf-send-message-phase-12 branch from 7d4b99e to c5135ac Compare April 21, 2026 08:33
@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 21, 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 Δ
.../TransactionDuplicate/DuplicateTransactionItem.tsx 0.00% <ø> (ø)
src/pages/inbox/report/PureReportActionItem.tsx 78.83% <100.00%> (+1.41%) ⬆️
src/pages/inbox/report/ReportActionItem.tsx 100.00% <ø> (ø)
...ages/inbox/report/ReportActionItemParentAction.tsx 0.00% <ø> (ø)
...ges/inbox/report/ReportActionsListItemRenderer.tsx 84.61% <ø> (ø)
...nents/Reactions/ReportActionItemEmojiReactions.tsx 46.15% <75.00%> (-3.85%) ⬇️
...rc/components/Reactions/ReactionTooltipContent.tsx 11.11% <0.00%> (ø)
... and 12 files with indirect coverage changes

@LukasMod LukasMod changed the title refactor: PureReportActionItem, ReportActionItemEmojiReactions [HOLD] refactor: PureReportActionItem, ReportActionItemEmojiReactions Apr 21, 2026
@LukasMod LukasMod marked this pull request as ready for review April 21, 2026 10:03
@LukasMod LukasMod requested review from a team as code owners April 21, 2026 10:03
@melvin-bot melvin-bot Bot requested review from dmkt9 and trjExpensify and removed request for a team April 21, 2026 10:03
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Apr 21, 2026

@dmkt9 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 April 21, 2026 10:03
Copy link
Copy Markdown

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

ℹ️ 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 thread src/pages/settings/Preferences/LanguagePage.tsx Outdated
@LukasMod
Copy link
Copy Markdown
Contributor Author

@codex review

Copy link
Copy Markdown

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

ℹ️ 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 thread src/components/Reactions/ReportActionItemEmojiReactions.tsx Outdated
@LukasMod LukasMod force-pushed the perf-send-message-phase-12 branch from ad5d9de to 7dee6a8 Compare April 21, 2026 14:15
@LukasMod
Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector
Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Nice work!

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

@dmkt9
Copy link
Copy Markdown
Contributor

dmkt9 commented Apr 21, 2026

@LukasMod, could you please retest this on iOS Safari and mobile Chrome? I noticed that ReportActionItemEmojiReactions is not appearing on those platforms.

ios.safari.mp4

@trjExpensify
Copy link
Copy Markdown
Contributor

PR doesn’t need product input as a refactor PR. Unassigning and unsubscribing myself.

@trjExpensify trjExpensify removed their request for review April 22, 2026 01:39
@LukasMod
Copy link
Copy Markdown
Contributor Author

@dmkt9 I added another video for iOS web and Android web. I don’t see this issue on my side. I’ve pulled the latest from main, could you check again? Also, these changes shouldn’t cause this behavior 🤔

@dmkt9
Copy link
Copy Markdown
Contributor

dmkt9 commented Apr 22, 2026

@dmkt9 I added another video for iOS web and Android web. I don’t see this issue on my side. I’ve pulled the latest from main, could you check again? Also, these changes shouldn’t cause this behavior 🤔

@LukasMod yes. I have reviewed your changes; they do not alter any behavior and look good to me. However, the issue occurred when I tested on those platforms, so let me test it again.

@LukasMod
Copy link
Copy Markdown
Contributor Author

Just resolved newest conflicts

@dmkt9
Copy link
Copy Markdown
Contributor

dmkt9 commented Apr 22, 2026

I can now reproduce the issue on staging. It appears to be a BE bug where the OpenReport API is not sending the reportActionsReactions_ data. It is strange that this only occurs on mobile browsers.

I will complete the checklist shortly.

@LukasMod
Copy link
Copy Markdown
Contributor Author

On videos (ios mobile safari) I also checked on staging and it was fine. Also checking this right now on https://staging.new.expensify.com, refreshing, adding new reactions in workspaces, DMs works well (iOS mobile safari)

@dmkt9
Copy link
Copy Markdown
Contributor

dmkt9 commented Apr 22, 2026

On videos (ios mobile safari) I also checked on staging and it was fine. Also checking this right now on staging.new.expensify.com, refreshing, adding new reactions in workspaces, DMs works well (iOS mobile safari)

Steps to reproduce: Navigate to "Troubleshoot > Clear cache and restart" in Safari on iOS, then return to a comment with at least one reaction. Note that reactions are no longer displayed.

@LukasMod
Copy link
Copy Markdown
Contributor Author

Can't repro on staging even with clear cache
https://github.com/user-attachments/assets/4d368c28-8e22-408c-a2e9-656c0a0167d7

@dmkt9
Copy link
Copy Markdown
Contributor

dmkt9 commented Apr 22, 2026

I can easily reproduce this on my end:
https://github.com/user-attachments/assets/3f154a89-1902-40fe-83ac-c3a9a70bd112

@dmkt9
Copy link
Copy Markdown
Contributor

dmkt9 commented Apr 22, 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
  • 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 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.hybrid.mp4
Android: mWeb Chrome
android.chrome.mp4
iOS: HybridApp
ios.native.mp4
iOS: mWeb Safari
ios.safari.mp4
MacOS: Chrome / Safari
mac.safari.mp4

Copy link
Copy Markdown
Contributor

@dmkt9 dmkt9 left a comment

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 cristipaval April 22, 2026 09:26
@cristipaval cristipaval merged commit 4672791 into Expensify:main Apr 22, 2026
33 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

🚧 @cristipaval 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.

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