Skip to content

Remove getReportTransactions callers' reliance on the deprecated default (Part 2) - #99656

Merged
Valforte merged 7 commits into
Expensify:mainfrom
linhvovan29546:refactor/66418-remove-getReportTransactions-p2
Sep 14, 2026
Merged

Valforte merged 7 commits into
Expensify:mainfrom
linhvovan29546:refactor/66418-remove-getReportTransactions-p2

Conversation

@linhvovan29546

@linhvovan29546 linhvovan29546 commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Remove getReportTransactions callers' reliance on the deprecated default (Part 2). getReportTransactions() falls back to a deprecated global when its allReportsTransactions parameter is omitted. This PR migrates two more callers outside ReportUtils.ts.

Explanation of Change

Continuation of Part 1 (#99633). Two more callers stop relying on getReportTransactions's deprecated-default fallback:

  • canApprove (ReportPreviewActionUtils.ts) is not exported and has exactly one caller (getReportPreviewAction, in the same file), which already always supplies transactions. The transactions ?? getReportTransactions(report?.reportID) fallback was dead code in practice, so transactions is now a required parameter and the fallback is removed.
  • hasDuplicateTransactions (TransactionUtils/index.ts) gains a required reportTransactions parameter. Its one caller, the useMoneyReportHeaderStatusBar hook, already computes the same report's transactions via useTransactionsAndViolationsForReport a few lines above (same underlying derived Onyx value useReportTransactionsCollection reads), so it's passed straight through instead of being recomputed off the deprecated global.

Both are pure data-threading changes — no behavior change, since the value now passed in is the same data the deprecated fallback would have produced.

Fixed Issues

$ #66418
PROPOSAL: N/A

Tests

  1. As a workspace approver, open the LHN preview of an expense report that's processing (submitted, awaiting your approval) with at least one valid expense. Confirm the report preview still shows the Approve action, exactly as before this change.
  2. Open a money request report that has two or more expenses flagged as duplicates. Confirm the report header still shows the Duplicates status bar, unchanged from before this PR.
  3. Open a money request report with no duplicate expenses and confirm the duplicates status bar does not appear.
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

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 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
Screen.Recording.2026-09-04.at.16.17.19.mov
Android: mWeb Chrome
Screen.Recording.2026-09-04.at.16.15.53.mov
iOS: Native
Screen.Recording.2026-09-04.at.16.19.33.mov
iOS: mWeb Safari
Screen.Recording.2026-09-04.at.16.12.51.mov
MacOS: Chrome / Safari
Screen.Recording.2026-09-04.at.16.11.14.mov

…ult (Part 2)

canApprove (ReportPreviewActionUtils.ts) is unexported and its one caller
already always supplies transactions, so drop the deprecated-default
fallback and make the param required. hasDuplicateTransactions
(TransactionUtils.ts) gains a required reportTransactions param, sourced
from data its one caller (a hook) already had via useTransactionsAndViolationsForReport.
@linhvovan29546 linhvovan29546 changed the title Remove getReportTransactions callers' reliance on the deprecated defa… Remove getReportTransactions callers' reliance on the deprecated default (Part 2) Aug 27, 2026
@codecov

codecov Bot commented Aug 27, 2026

Copy link
Copy Markdown

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/hooks/useMoneyReportHeaderStatusBar.ts 76.56% <100.00%> (+76.56%) ⬆️
src/libs/ReportPreviewActionUtils.ts 91.59% <100.00%> (-0.08%) ⬇️
src/libs/TransactionUtils/index.ts 92.52% <ø> (+0.12%) ⬆️
... and 13 files with indirect coverage changes

…-getReportTransactions-p2

# Conflicts:
#	src/libs/ReportPreviewActionUtils.ts
…teTransactions call

Codecov flagged 0% patch coverage on PR Expensify#99656 for the line threading
transactions into hasDuplicateTransactions. This hook had no test
exercising its real implementation before now.
Use require() instead of a static namespace import for ReportUtils
spies, since a wildcard import can't be statically proven not to touch
the restricted isPaidGroupPolicy/isPaidGroupPolicyExpenseReport
exports. Also switch to .at() for array element access per the
project's array-access rule.
Array.prototype.at() on a tuple widens to the union of all parameter
types, so casting its result back down tripped
@typescript-eslint/no-unsafe-type-assertion. Assert the full call
args via toHaveBeenCalledWith instead of indexing into mock.calls.
@linhvovan29546
linhvovan29546 marked this pull request as ready for review September 4, 2026 09:35
@linhvovan29546
linhvovan29546 requested review from a team as code owners September 4, 2026 09:35
@melvin-bot
melvin-bot Bot requested review from DylanDylann and removed request for a team September 4, 2026 09:35
@melvin-bot

melvin-bot Bot commented Sep 4, 2026

Copy link
Copy Markdown

@DylanDylann 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 garrettmknight and removed request for a team September 4, 2026 09:35
Comment thread tests/unit/hooks/useMoneyReportHeaderStatusBarTest.ts Outdated
Addresses CONSISTENCY-16 review bot feedback on PR Expensify#99656.
@garrettmknight
garrettmknight removed their request for review September 4, 2026 11:35
@linhvovan29546

Copy link
Copy Markdown
Contributor Author

@DylanDylann Could you please check this one when you have a chance? Thanks

@DylanDylann

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

Screen.Recording.2026-09-11.at.15.53.18.mov

@melvin-bot
melvin-bot Bot requested a review from Valforte September 11, 2026 08:54
@DylanDylann

Copy link
Copy Markdown
Contributor

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Can't wait for the next one!

Reviewed commit: 1509ebf0eb

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

@Valforte Valforte 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.

Looks good!

@Valforte
Valforte merged commit 938cb24 into Expensify:main Sep 14, 2026
35 of 37 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

🚧 Valforte 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/Valforte in version: 9.4.78-0 🚀

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

@MelvinBot

MelvinBot commented Sep 15, 2026

Copy link
Copy Markdown
Contributor

🤖 No help site changes required. I did not create a docs PR.

Why: This PR is an internal refactor. It threads an existing transactions array into canApprove and hasDuplicateTransactions instead of letting them fall back to the deprecated getReportTransactions() default. No user-facing behavior, copy, setting, or flow changes.

What I checked

Changed files, all internal:

  • src/libs/ReportPreviewActionUtils.tstransactions becomes a required parameter on the non-exported canApprove; its single caller already passes it.
  • src/libs/TransactionUtils/index.tshasDuplicateTransactions gains a required reportTransactions parameter.
  • src/hooks/useMoneyReportHeaderStatusBar.ts — passes the already-computed transactions through.
  • tests/unit/hooks/useMoneyReportHeaderStatusBarTest.ts — new unit test.

The two behaviors touched are the report preview Approve action and the Duplicates status bar on an expense report header. Both render exactly as before, since the value passed in is the same data the deprecated fallback produced. The help site describes when those appear, not how the data is fetched, so nothing under docs/articles goes stale.

I also scanned docs/articles for duplicate-expense and approval content. The matches describe user-facing rules (for example, duplicate detection and approval workflows) that this PR does not alter.

If you think a specific article does need updating, reply with @MelvinBot and the article path and I'll draft the change.

You asked me to close with the line below. There is no linked help site PR in this case, so treat it as not applicable:

@linhvovan29546, please review the linked help site PR and confirm it reflects the current behavior. Then mark the linked help site PR Ready for review


view run · no recording available

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/luacmartins in version: 9.4.78-3 🚀

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