Skip to content

Decompose MoneyRequestConfirmationList into view-model hooks#88720

Open
OlimpiaZurek wants to merge 3 commits intoExpensify:mainfrom
callstack-internal:decompose-MoneyRequestConfirmationList
Open

Decompose MoneyRequestConfirmationList into view-model hooks#88720
OlimpiaZurek wants to merge 3 commits intoExpensify:mainfrom
callstack-internal:decompose-MoneyRequestConfirmationList

Conversation

@OlimpiaZurek
Copy link
Copy Markdown
Contributor

@OlimpiaZurek OlimpiaZurek commented Apr 24, 2026

Explanation of Change

MoneyRequestConfirmationList had grown to ~1,211 lines, mixing rendering with business logic for policy/category/tag fetching, distance/tax/amount derivation, split-share dispatch, validation, error translation, and section building. This PR extracts that logic into focused hooks and one component:

  • useFormErrorManagement — owns form-error state + translated errorMessage, replacing the inline fallback ladder
  • useConfirmationValidation / useConfirmAction — own the validate+submit path, including delegate-access gating and split-bill fan-out
  • useSplitParticipants — owns split rows and onSplitShareChange dispatch, so the parent no longer derives the callback
  • useConfirmationSections — owns the SelectionList section data; parent no longer imports Section or section helpers
  • useTransactionReportForConfirmation — fetches the thread report via useOnyx with a narrow .type-only selector
  • usePolicyCategoriesForConfirmation / usePolicyTagsForConfirmation — own the collection subs (draft + real), eliminating parent re-renders on every POLICY_CATEGORIES / POLICY_TAGS fire
  • useDistanceRequestState / useTaxAmount / useConfirmationAmount / useConfirmationCtaText — own their respective derivation chains
    - useReceiptTraining — owns test-receipt detection + product-training tooltip wiring; parent no longer calls useProductTrainingContext
    ConfirmationFooterContent — renders the CTA + error surface as a dedicated subtree, replacing the inline listFooterContent JSX

Dead code removed: unused translate/useLocalize, duplicate routeError, inline onSplitShareChange and errorMessage memos, and parent imports of setIndividualShare, convertToBackendAmount, getIOUConfirmationOptionsFromPayeePersonalDetail, isSelectedManagerMcTest, useProductTrainingContext, and Section.

The net result is MoneyRequestConfirmationList going from ~1,211 lines to ~625 lines, with data subscriptions and action logic owned by the hooks that have the right data access

Fixed Issues

$ #88725
PROPOSAL:

Tests

  • Verify that no errors appear in the JS console
  1. Open an expense chat, then FAB → Create expense → Manual
  2. Enter an amount and select a participant; verify the confirmation screen opens
  3. Verify all fields render correctly: amount, merchant, category, tag, tax, attendees, description, date, billable toggle, and receipt preview (when present)
  4. Tap the confirm CTA and verify the expense is created on the correct report with correct data

Offline tests

QA Steps

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

same as tests

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

@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 24, 2026

@OlimpiaZurek OlimpiaZurek marked this pull request as ready for review April 24, 2026 14:03
@OlimpiaZurek OlimpiaZurek requested review from a team as code owners April 24, 2026 14:03
@melvin-bot melvin-bot Bot requested review from marcochavezf and trjExpensify and removed request for a team April 24, 2026 14:03
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Apr 24, 2026

@marcochavezf 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]

enterKeyEventListenerPriority={1}
useKeyboardShortcuts
// eslint-disable-next-line @typescript-eslint/prefer-nullish-coalescing
isLoading={isConfirmed || isConfirming}
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.

❌ CONSISTENCY-5 (docs)

This eslint-disable-next-line @typescript-eslint/prefer-nullish-coalescing lacks a justification comment. The disable is needed because isConfirmed and isConfirming are boolean | undefined and || intentionally treats false as falsy (desired for isLoading), but that reasoning should be documented.

Add a justification comment, for example:

// eslint-disable-next-line @typescript-eslint/prefer-nullish-coalescing -- Using || because we want undefined and false to both be treated as falsy for isLoading
isLoading={isConfirmed || isConfirming}

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

enterKeyEventListenerPriority={1}
useKeyboardShortcuts
// eslint-disable-next-line @typescript-eslint/prefer-nullish-coalescing
isLoading={isConfirmed || isConfirming || isLoadingReceipt}
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.

❌ CONSISTENCY-5 (docs)

This eslint-disable-next-line @typescript-eslint/prefer-nullish-coalescing lacks a justification comment. Same situation as above -- || is intentional because isConfirmed, isConfirming, and isLoadingReceipt include boolean | undefined types.

Add a justification comment, for example:

// eslint-disable-next-line @typescript-eslint/prefer-nullish-coalescing -- Using || because we want undefined and false to both be treated as falsy for isLoading
isLoading={isConfirmed || isConfirming || isLoadingReceipt}

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

@trjExpensify trjExpensify removed their request for review April 24, 2026 14:43
@trjExpensify
Copy link
Copy Markdown
Contributor

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

@mountiny
Copy link
Copy Markdown
Contributor

@codex review

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR refactors MoneyRequestConfirmationList by extracting its business logic, Onyx subscriptions, validation, derivations, and footer rendering into dedicated hooks and a footer component—aiming to reduce component size and limit re-renders in the Create Expense confirmation flow.

Changes:

  • Added a suite of confirmation-focused hooks (policy categories/tags, report subscription, validation/confirm action, amount/tax/distance derivations, split participants, receipt training, section building, and form-error management).
  • Introduced ConfirmationFooterContent as a dedicated CTA + error surface subtree.
  • Updated MoneyRequestConfirmationList to consume the new hooks/components and removed inlined logic/imports accordingly.

Reviewed changes

Copilot reviewed 15 out of 15 changed files in this pull request and generated 4 comments.

Show a summary per file
File Description
src/components/MoneyRequestConfirmationList/hooks/useTransactionReportForConfirmation.ts Adds a narrowed report subscription (type-only selector) for confirmation logic.
src/components/MoneyRequestConfirmationList/hooks/useTaxAmount.ts Extracts tax code/value selection and tax amount derivation into a hook.
src/components/MoneyRequestConfirmationList/hooks/useSplitParticipants.tsx Extracts split participant row construction and split share dispatch/reset UI.
src/components/MoneyRequestConfirmationList/hooks/useReceiptTraining.ts Extracts test-receipt/test-drive/Manager McTest training tooltip state.
src/components/MoneyRequestConfirmationList/hooks/usePolicyTagsForConfirmation.ts Extracts policy-tag Onyx subscription + derived tag list ordering.
src/components/MoneyRequestConfirmationList/hooks/usePolicyCategoriesForConfirmation.ts Extracts real/draft policy categories subscriptions with fallback.
src/components/MoneyRequestConfirmationList/hooks/useFormErrorManagement.ts Centralizes form error state, debouncing, violation clearing, and error message derivation.
src/components/MoneyRequestConfirmationList/hooks/useDistanceRequestState.ts Extracts distance request rate/unit/currency derivation and recalculation flags.
src/components/MoneyRequestConfirmationList/hooks/useConfirmationValidation.ts Extracts pure validation checks into a reusable hook returning structured results.
src/components/MoneyRequestConfirmationList/hooks/useConfirmationSections.ts Extracts SelectionList section-building (split vs non-split) into a hook.
src/components/MoneyRequestConfirmationList/hooks/useConfirmationCtaText.ts Extracts confirm CTA label derivation into a hook returning dropdown options.
src/components/MoneyRequestConfirmationList/hooks/useConfirmationAmount.ts Extracts confirmation amount formatting + per-attendee calculation logic.
src/components/MoneyRequestConfirmationList/hooks/useConfirmAction.ts Extracts confirm click handler (invoice routing, validate, confirm/send-money side effects).
src/components/MoneyRequestConfirmationList/ConfirmationFooterContent.tsx Adds a dedicated footer component for CTA + error rendering and tooltip wiring.
src/components/MoneyRequestConfirmationList.tsx Wires the extracted hooks/components into the main confirmation list and removes inlined logic.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +133 to +134
const isSplitModified = !!transaction?.splitShares && Object.keys(transaction.splitShares).some((key) => transaction.splitShares?.[Number(key) ?? -1]?.isModified);

Copy link

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

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

isSplitModified is computed on every render via Object.keys(...).some(...). In the original component this was memoized; keeping it un-memoized here can reintroduce avoidable work during typing in split inputs. Consider restoring useMemo keyed off transaction?.splitShares (or deriving it inside the existing splitParticipants memo).

Suggested change
const isSplitModified = !!transaction?.splitShares && Object.keys(transaction.splitShares).some((key) => transaction.splitShares?.[Number(key) ?? -1]?.isModified);
const isSplitModified = useMemo(() => {
if (!transaction?.splitShares) {
return false;
}
return Object.keys(transaction.splitShares).some((key) => transaction.splitShares?.[Number(key) ?? -1]?.isModified);
}, [transaction?.splitShares]);

Copilot uses AI. Check for mistakes.
Comment on lines +135 to +154
const getSplitSectionHeader = () => (
<View style={[styles.mt2, styles.mb1, styles.flexRow, styles.justifyContentBetween]}>
<Text style={[styles.ph5, styles.textLabelSupporting]}>{translate('iou.participants')}</Text>
{!shouldShowReadOnlySplits && !!isSplitModified && (
<PressableWithFeedback
onPress={() => {
// Dismiss the keyboard so that MoneyRequestAmountInput's useEffect syncs the new amount.
// Without this, the effect skips the update while the input is focused (see formatAmountOnBlur guard).
Keyboard.dismiss();
resetSplitShares(transaction);
}}
accessibilityLabel={CONST.ROLE.BUTTON}
role={CONST.ROLE.BUTTON}
shouldUseAutoHitSlop
sentryLabel={CONST.SENTRY_LABEL.REQUEST_CONFIRMATION_LIST.RESET_SPLIT_SHARES}
>
<Text style={[styles.pr5, styles.textLabelSupporting, styles.link]}>{translate('common.reset')}</Text>
</PressableWithFeedback>
)}
</View>
Copy link

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

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

getSplitSectionHeader is recreated on every render (not wrapped in useCallback/useMemo). Since useConfirmationSections depends on this function, it will invalidate that memo each render and can cause unnecessary section recalculation. Make the header builder stable (e.g. useCallback) or return the header element directly as a memoized value.

Suggested change
const getSplitSectionHeader = () => (
<View style={[styles.mt2, styles.mb1, styles.flexRow, styles.justifyContentBetween]}>
<Text style={[styles.ph5, styles.textLabelSupporting]}>{translate('iou.participants')}</Text>
{!shouldShowReadOnlySplits && !!isSplitModified && (
<PressableWithFeedback
onPress={() => {
// Dismiss the keyboard so that MoneyRequestAmountInput's useEffect syncs the new amount.
// Without this, the effect skips the update while the input is focused (see formatAmountOnBlur guard).
Keyboard.dismiss();
resetSplitShares(transaction);
}}
accessibilityLabel={CONST.ROLE.BUTTON}
role={CONST.ROLE.BUTTON}
shouldUseAutoHitSlop
sentryLabel={CONST.SENTRY_LABEL.REQUEST_CONFIRMATION_LIST.RESET_SPLIT_SHARES}
>
<Text style={[styles.pr5, styles.textLabelSupporting, styles.link]}>{translate('common.reset')}</Text>
</PressableWithFeedback>
)}
</View>
const getSplitSectionHeader = useCallback(
() => (
<View style={[styles.mt2, styles.mb1, styles.flexRow, styles.justifyContentBetween]}>
<Text style={[styles.ph5, styles.textLabelSupporting]}>{translate('iou.participants')}</Text>
{!shouldShowReadOnlySplits && !!isSplitModified && (
<PressableWithFeedback
onPress={() => {
// Dismiss the keyboard so that MoneyRequestAmountInput's useEffect syncs the new amount.
// Without this, the effect skips the update while the input is focused (see formatAmountOnBlur guard).
Keyboard.dismiss();
resetSplitShares(transaction);
}}
accessibilityLabel={CONST.ROLE.BUTTON}
role={CONST.ROLE.BUTTON}
shouldUseAutoHitSlop
sentryLabel={CONST.SENTRY_LABEL.REQUEST_CONFIRMATION_LIST.RESET_SPLIT_SHARES}
>
<Text style={[styles.pr5, styles.textLabelSupporting, styles.link]}>{translate('common.reset')}</Text>
</PressableWithFeedback>
)}
</View>
),
[
styles.mt2,
styles.mb1,
styles.flexRow,
styles.justifyContentBetween,
styles.ph5,
styles.textLabelSupporting,
styles.pr5,
styles.link,
translate,
shouldShowReadOnlySplits,
isSplitModified,
transaction,
],

Copilot uses AI. Check for mistakes.
Comment on lines +13 to +21
type UseConfirmationSectionsParams = {
isTypeSplit: boolean;
shouldHideToSection: boolean;
canEditParticipant: boolean;
payeePersonalDetails: OnyxEntry<OnyxTypes.PersonalDetails> | CurrentUserPersonalDetails;
splitParticipants: MoneyRequestConfirmationListItem[];
selectedParticipants: Participant[];
getSplitSectionHeader: () => React.JSX.Element;
};
Copy link

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

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

UseConfirmationSectionsParams references React.JSX.Element but this module doesn’t import React, which will fail TypeScript compilation under strict (no global React namespace). Import React as a type (or switch the type to JSX.Element).

Copilot uses AI. Check for mistakes.
Comment on lines +22 to +36
type UseConfirmationValidationParams = {
transaction: OnyxTypes.Transaction | undefined;
transactionReport: OnyxTypes.Report | undefined;
transactionID: string | undefined;
iouType: IOUType;
iouAmount: number;
iouMerchant: string | undefined;
iouCategory: string;
iouCurrencyCode: string;
iouAttendees: Attendee[];
policy: OnyxTypes.Policy | undefined;
policyTags: OnyxTypes.PolicyTagLists | undefined;
policyTagLists: ReturnType<typeof getTagListsFn>;
policyCategories: OnyxTypes.PolicyCategories | undefined;
selectedParticipants: Participant[];
Copy link

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

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

The hook parameter types don’t match how it’s called from MoneyRequestConfirmationList: transaction, transactionReport, policy, policyTags, policyCategories are passed as OnyxEntry<...> (nullable), but the hook types only allow ... | undefined. With strict TS this is not assignable (null isn’t allowed). Update the param types to accept OnyxEntry (or include null) consistently.

Copilot uses AI. Check for mistakes.
@mountiny mountiny requested a review from mkhutornyi April 24, 2026 15:08
@mountiny
Copy link
Copy Markdown
Contributor

@mkhutornyi all yours

@chatgpt-codex-connector
Copy link
Copy Markdown

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

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

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