Skip to content

refactor: Remove deprecated report name functions in ReportUtils (Part 4) - Hubert's fork#85975

Merged
neil-marcellini merged 23 commits intoExpensify:mainfrom
callstack-internal:fix/76852-part4
Mar 20, 2026
Merged

refactor: Remove deprecated report name functions in ReportUtils (Part 4) - Hubert's fork#85975
neil-marcellini merged 23 commits intoExpensify:mainfrom
callstack-internal:fix/76852-part4

Conversation

@sosek108
Copy link
Contributor

Explanation of Change

Migrates non-component call sites from the deprecated ReportUtils.getReportName to ReportNameUtils.getReportName, passing report (and optionally reportAttributes) directly as arguments.

Task.ts
BrowserNotifications.ts
ModifiedExpenseMessage.ts
SearchQueryUtils.ts
MoneyRequestReportPreviewContent.tsx
MoneyRequestReportPreview.test.tsx

Fixed Issues

$ #76852
PROPOSAL:

Tests

  1. Task Share Destination (Task.ts)
    getShareDestination uses getReportName to display the name of the report a task is being shared/assigned to.

Test Steps:

Open the app and navigate to a workspace with multiple reports.
Create a new task (e.g., from the + menu → Task).
Tap the Assignee or Share destination field.
Verify report names appear correctly in the destination list (e.g., workspace expense chats, DMs, group rooms).
Assign the task to a workspace expense chat and submit.
Verify the task is created with the correct destination name shown.
2. Browser/Desktop Notification — Room or Group Chat Comment (BrowserNotifications.ts, LocalNotification/index.ts)
pushReportCommentNotification uses getReportName as the notification title for rooms/group chats.

Test Steps:

Use two browser tabs logged in as two different accounts (or use two devices).
Open a Group Chat or a Room (#admins, #announce, etc.) in Account A.
From Account B, send a message into that same group chat or room.
On Account A's desktop/web, verify a browser notification pops up.
Verify the notification title matches the exact room/group chat name as displayed in the LHN.
3. Modified Expense Notification — Expense Moved Between Reports (ModifiedExpenseMessage.ts, BrowserNotifications.ts)
getMovedFromOrToReportMessage uses getReportName for the "moved from report" text in the notification.

Test Steps:

Create an expense and submit it to a workspace report (Report A).
While logged in as an admin on another browser/device, move that expense to a different report (Report B).
On either account, open Report A and scroll to find the system/automated message about the moved expense.
Verify the message reads something like "Moved from [Report A name]" — confirming the report name resolves correctly (not undefined, blank, or a raw report ID).
Open Report B and verify that a corresponding message appears there as well.
4. Search — "In" Filter Display Value (SearchQueryUtils.ts, SearchPageHeaderInput.tsx, buildSubstitutionsMap.ts)
getFilterDisplayValue for filterName === CONST.SEARCH.SYNTAX_FILTER_KEYS.IN uses getReportName to resolve a report ID to a human-readable name. buildUserReadableQueryString and buildSubstitutionsMap now propagate reportAttributes.

Test Steps:

Open the Search page and click/focus the search input.
Type in: and select a specific report/room from the autocomplete suggestions.
Verify the report name appears inline in the search input as styled text (not a raw report ID like in:123456789).
Submit the search.
Verify the query display bar below the input shows the human-readable report name (e.g., in: My Room) instead of the raw ID.
Navigate away (e.g., open a report) and return to Search via the LHN — verify the query bar still shows the correct report name.
Repeat with a #room, a DM, and a group chat to cover different report type name resolutions.
5. Money Request Report Preview Header (MoneyRequestReportPreviewContent.tsx)
getReportName(iouReport, reportAttributes) is used as the heading text of the MoneyRequestReportPreview component (the preview card visible in the 1:1 chat).

Test Steps:

Open a 1:1 chat where an IOU/expense report exists.
Locate the MoneyRequestReportPreview card in the chat thread.
Verify the header shows the correct IOU/expense report name (e.g., "Expense Report" or a custom report name).
Open a workspace-based expense report and find its preview card — verify the name matches the report's actual name.
If the report has a custom reportName, verify that custom name is shown.
6. Pusher-Triggered Notifications (User.ts, Report/index.ts)
triggerNotifications in User.ts now passes reportAttributes?.reports to showReportActionNotification, which then threads it through to both showCommentNotification and showModifiedExpenseNotification.

Test Steps:

Have two accounts open simultaneously.
From Account B, send a message in a Room chatting with Account A.
Verify Account A receives a browser notification with the correct room name as the title.
From Account B, send a message in a 1:1 DM with Account A.
Verify Account A's notification title shows the sender's name (not the room name path).
Verify that no errors appear in the JS console

Offline tests

Same as tests.

QA Steps

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

Same as tests.

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

@sosek108 sosek108 requested review from a team as code owners March 20, 2026 17:32
@melvin-bot melvin-bot bot requested review from eVoloshchak and removed request for a team March 20, 2026 17:32
@melvin-bot
Copy link

melvin-bot bot commented Mar 20, 2026

@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 JmillsExpensify and removed request for a team March 20, 2026 17:32
@sosek108
Copy link
Contributor Author

Copy link
Contributor

@neil-marcellini neil-marcellini left a comment

Choose a reason for hiding this comment

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

looking pretty good, just a few tests that should be updated I think

Comment on lines -167 to -194
it('calls initializePusher when SIGN_IN_MODAL is active and conciergeReportID is loaded', async () => {
mockedIsActiveRoute.mockReturnValue(true);

const conciergeReportID = '67890';

await Onyx.merge(ONYXKEYS.SESSION, {accountID: TEST_ACCOUNT_ID, email: 'test@test.com'});
await Onyx.merge(ONYXKEYS.CONCIERGE_REPORT_ID, conciergeReportID);
await waitForBatchedUpdates();

renderAuthScreensInitHandler();
await waitForBatchedUpdatesWithAct();

// subscribeToUserEvents should be called with conciergeReportID from both mount and sign-in modal effects
expect(subscribeToUserEvents).toHaveBeenCalledWith(TEST_ACCOUNT_ID, expect.any(Function));
});

it('does not call initializePusher from sign-in modal effect when conciergeReportID is still loading', async () => {
mockedIsActiveRoute.mockReturnValue(true);

await Onyx.merge(ONYXKEYS.SESSION, {accountID: TEST_ACCOUNT_ID, email: 'test@test.com'});
await waitForBatchedUpdates();

renderAuthScreensInitHandler();
await waitForBatchedUpdatesWithAct();

// The mount effect calls subscribeToUserEvents with undefined conciergeReportID
expect(subscribeToUserEvents).toHaveBeenCalledWith(TEST_ACCOUNT_ID, expect.any(Function));
});
Copy link
Contributor

Choose a reason for hiding this comment

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

Sorry if I was unclear before, but I don't think we should remove these tests. I think they're just using Concierge Report ID as an example report to test certain things, so let's figure out a better way to test this.

Also, in the name of the test or the description, it talks about initialize pusher, and I think that's synonymous with subscribe to user events.

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: 5f92362835

ℹ️ 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 Mar 20, 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 Δ
...ReportPreview/MoneyRequestReportPreviewContent.tsx 60.94% <ø> (-0.94%) ⬇️
src/components/Search/SearchAutocompleteList.tsx 71.76% <ø> (ø)
.../Search/SearchPageHeader/SearchPageHeaderInput.tsx 50.00% <100.00%> (ø)
...nents/Search/SearchRouter/buildSubstitutionsMap.ts 100.00% <ø> (ø)
src/hooks/useSearchTypeMenu.tsx 69.33% <100.00%> (ø)
src/libs/ModifiedExpenseMessage.ts 90.09% <100.00%> (ø)
...Navigation/AppNavigator/AuthScreensInitHandler.tsx 96.92% <100.00%> (ø)
src/libs/SearchQueryUtils.ts 76.20% <100.00%> (ø)
src/libs/actions/Report/index.ts 67.83% <100.00%> (ø)
src/libs/actions/Task.ts 46.66% <ø> (ø)
... and 5 more
... and 12 files with indirect coverage changes

@neil-marcellini
Copy link
Contributor

We previously had a C+ review, and pretty sure the changes since then are fine, so we can merge this.

@neil-marcellini neil-marcellini merged commit b51e63c into Expensify:main Mar 20, 2026
28 of 29 checks passed
@github-actions
Copy link
Contributor

🚧 @neil-marcellini has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify
Copy link
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
Contributor

🚀 Deployed to staging by https://github.com/neil-marcellini in version: 9.3.42-0 🚀

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.

4 participants