Skip to content

perf: Split TransactionItemRow into narrow and wide versions#89120

Merged
luacmartins merged 18 commits into
Expensify:mainfrom
software-mansion-labs:perf/split-transaction-item-row
May 13, 2026
Merged

perf: Split TransactionItemRow into narrow and wide versions#89120
luacmartins merged 18 commits into
Expensify:mainfrom
software-mansion-labs:perf/split-transaction-item-row

Conversation

@jmusial
Copy link
Copy Markdown
Contributor

@jmusial jmusial commented Apr 28, 2026

Explanation of Change

Split TransactionItemRow (the inner data-row) and TransactionListItem (the outer search-list item) into viewport-specific variants — *Wide (table layout) and *Narrow (mobile layout) — so each viewport only loads the code, column renderers, and dependencies it actually needs.

Also introduced three deferred-rendering wrappers.

  • DeferredActionCell — renders a pulsing skeleton on first paint, then swaps in the real ActionCell after a transition
  • DeferredChatBubbleCell — same pattern for the comment-count bubble icon
  • DeferredTransactionItemRowRBR — defers the RBR (red-brick-road) violation/error row

This keeps large search result lists responsive on initial render by letting React paint the visible shell immediately and hydrate heavier sub-trees in a lower-priority pass.

Note: this PR overlaps with #89083

Perf gains

image image

Fixed Issues

$ #89123
PROPOSAL:

Tests

  1. Start Spend/Reports
  2. Navigate to Spend/Expenses
  3. Should work as prod with possible skeleton loader on certain components

Offline tests

Same as 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 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

MacOS: Chrome / Safari
Screen.Recording.2026-04-29.at.15.56.23.mov

@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 28, 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 Δ
...actionItemRow/DataCells/DeferredChatBubbleCell.tsx 100.00% <100.00%> (ø)
...ansactionItemRow/DeferredTransactionItemRowRBR.tsx 100.00% <100.00%> (ø)
...ents/TransactionItemRow/TransactionItemRowWide.tsx 95.00% <95.00%> (ø)
src/components/TransactionItemRow/index.tsx 82.53% <72.41%> (-0.60%) ⬇️
...ts/TransactionItemRow/TransactionItemRowNarrow.tsx 0.00% <0.00%> (ø)
.../TransactionListItem/TransactionListItemNarrow.tsx 0.00% <0.00%> (ø)
...em/TransactionListItem/TransactionListItemWide.tsx 0.00% <0.00%> (ø)
.../SearchList/ListItem/TransactionListItem/index.tsx 0.00% <0.00%> (ø)
... and 12 files with indirect coverage changes

@jmusial jmusial changed the title Split TransactionItemRow into narrow and wide versions perf: Split TransactionItemRow into narrow and wide versions Apr 28, 2026
@jmusial
Copy link
Copy Markdown
Contributor Author

jmusial commented Apr 29, 2026

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

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

taxAmountColumnSize={CONST.SEARCH.TABLE_COLUMN_SIZES.NORMAL}
shouldShowCheckbox={!!canSelectMultiple}
checkboxSentryLabel={CONST.SENTRY_LABEL.SEARCH.TRANSACTION_LIST_ITEM_CHECKBOX}
style={[styles.p3, styles.pv2, shouldUseNarrowLayout ? [styles.p0, styles.pt3] : [styles.noBorderRadius]]}
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Keep narrow transaction rows square-cornered

The narrow list path no longer includes styles.noBorderRadius when rendering TransactionItemRow, but TransactionItemRowNarrow still applies styles.expenseWidgetRadius internally. On small screens this reintroduces rounded inner corners in hydrated search rows, while the static placeholder list still uses square corners, causing a visible shape jump when the real list replaces the static one and breaking the stated narrow-layout visual parity.

Useful? React with 👍 / 👎.

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.

Not valid. No shape jump occurs in practice. The radius would only become visible on a selected row, which isn't the scenario (inner bgActiveStyles is empty for unselected rows, so expenseWidgetRadius has no background to clip and is visually a no-op)

isDescription={!merchant}
/>
) : null}
<View style={[styles.flexRow, styles.alignItemsCenter, styles.gap2]}>
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P3 Badge Right-align amount block when merchant text is absent

The trailing amount/comments container is always rendered without the previous conditional mlAuto, so when merchantOrDescription is empty the row has only one child in this justifyContentBetween section and it sits at the left instead of the right. This misaligns amount/comment content for transactions without merchant/description (common for partial scans or missing fields).

Useful? React with 👍 / 👎.

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.

True, the !merchantOrDescription && styles.mlAuto was added on main after the split of TransactionItemRow, so the merge didn't carry it over

@jmusial jmusial marked this pull request as ready for review April 29, 2026 14:10
@jmusial jmusial requested review from a team as code owners April 29, 2026 14:10
@melvin-bot melvin-bot Bot requested review from ChavdaSachin and heyjennahay and removed request for a team April 29, 2026 14:10
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Apr 29, 2026

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

@jmusial
Copy link
Copy Markdown
Contributor Author

jmusial commented Apr 29, 2026

I'll be OOO until 10 May. @OlGierd03 will be looking after this PR until then.


// eslint-disable-next-line react/jsx-props-no-spreading
return <ChatBubbleCell {...props} />;
}
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)

The eslint-disable-next-line react/jsx-props-no-spreading lacks a comment explaining why the rule is disabled.

Add a justification comment:

// Deferred wrapper intentionally forwards all props to the underlying component
// eslint-disable-next-line react/jsx-props-no-spreading
return <ChatBubbleCell {...props} />;

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

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.

Comment added

}

// eslint-disable-next-line react/jsx-props-no-spreading
return <TransactionItemRowRBR {...props} />;
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)

The eslint-disable-next-line react/jsx-props-no-spreading lacks a comment explaining why the rule is disabled.

Add a justification comment:

// Deferred wrapper intentionally forwards all props to the underlying component
// eslint-disable-next-line react/jsx-props-no-spreading
return <TransactionItemRowRBR {...props} />;

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

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.

Comment added

import DeferredTransactionItemRowRBR from './DeferredTransactionItemRowRBR';
import type {TransactionItemRowNarrowComputedData, TransactionItemRowProps} from './types';

type TransactionItemRowNarrowProps = Omit<TransactionItemRowProps, 'shouldUseNarrowLayout' | 'policyForMovingExpenses'> & TransactionItemRowNarrowComputedData;
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-4 (docs)

TransactionItemRowNarrowProps is defined as Omit<TransactionItemRowProps, 'shouldUseNarrowLayout' | 'policyForMovingExpenses'> & TransactionItemRowNarrowComputedData, which pulls in many wide-layout-only props that the narrow component never destructures or uses: dateColumnSize, submittedColumnSize, approvedColumnSize, postedColumnSize, exportedColumnSize, amountColumnSize, taxAmountColumnSize, isReportItemChild, isActionColumnWide, isHover, isLargeScreenWidth, onButtonPress, isActionLoading, shouldHighlightItemWhenSelected, columns, reportActions, nonPersonalAndWorkspaceCards, and policy.

Define a narrow-specific props type using Pick that only includes props the component actually uses:

type TransactionItemRowNarrowProps = Pick<TransactionItemRowProps,
  'transactionItem' | 'report' | 'isSelected' | 'shouldShowTooltip' |
  'onCheckboxPress' | 'shouldShowCheckbox' | 'style' |
  'isInSingleTransactionReport' | 'shouldShowRadioButton' |
  'onRadioButtonPress' | 'shouldShowErrors' | 'isDisabled' |
  'violations' | 'shouldShowBottomBorder' | 'onArrowRightPress' |
  'shouldShowArrowRightOnNarrowLayout' | 'checkboxSentryLabel'
> & TransactionItemRowNarrowComputedData;

This also means the parent dispatcher should construct narrow-only props instead of spreading all sharedProps.


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

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.

I changed the narrow type to a Pick of the props that are actually used. I also dropped the now unused isDeletedTransaction from the computed data type, since neither variant reads it (the TransactionItemRowWide now computes it within the function)

@ChavdaSachin
Copy link
Copy Markdown
Contributor

@OlGierd03, please take a look at the AI review comments and let me know when the PR is ready for the review.

@OlGierd03
Copy link
Copy Markdown
Contributor

Sure thing, I'll get around to it soon

@OlGierd03
Copy link
Copy Markdown
Contributor

Sorry for the delay. I haven't had time to work on this over the last few days. I'm getting right to it now, though

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 optimizes large transaction search/result lists by splitting TransactionItemRow and TransactionListItem into Narrow (mobile) and Wide (table) variants, and by deferring heavier subtrees (action cell, comment bubble, and RBR row) to improve first-paint responsiveness.

Changes:

  • Added viewport-specific TransactionItemRowNarrow / TransactionItemRowWide and updated the TransactionItemRow dispatcher to compute and forward layout-specific data.
  • Split TransactionListItem into TransactionListItemNarrow / TransactionListItemWide with a new dispatcher entrypoint.
  • Introduced deferred-render wrappers (DeferredActionCell, DeferredChatBubbleCell, DeferredTransactionItemRowRBR) to delay expensive UI until after initial paint.

Reviewed changes

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

Show a summary per file
File Description
src/components/TransactionItemRow/types.ts Introduces shared and variant-specific prop/computed-data types for the split row implementations.
src/components/TransactionItemRow/TransactionItemRowWide.tsx New wide/table implementation for transaction rows (columns-based rendering + deferred cells).
src/components/TransactionItemRow/TransactionItemRowNarrow.tsx New narrow/mobile implementation for transaction rows (compact stacked layout + deferred cells).
src/components/TransactionItemRow/index.tsx Refactors the original component into a dispatcher that computes shared data and selects narrow vs wide variants.
src/components/TransactionItemRow/DeferredTransactionItemRowRBR.tsx Defers rendering of the RBR (violation/error) row.
src/components/TransactionItemRow/DataCells/TransactionDataCellProps.ts Updates the TransactionWithOptionalSearchFields type import to the new types module.
src/components/TransactionItemRow/DataCells/DeferredChatBubbleCell.tsx Defers chat-bubble rendering with a skeleton placeholder.
src/components/Search/SearchList/ListItem/TransactionListItem/types.ts Adds shared narrow/wide prop types for split transaction list items.
src/components/Search/SearchList/ListItem/TransactionListItem/TransactionListItemWide.tsx New wide/table list-item wrapper that renders a transaction row in table layout.
src/components/Search/SearchList/ListItem/TransactionListItem/TransactionListItemNarrow.tsx New narrow/mobile list-item wrapper that includes the user info row + narrow transaction row.
src/components/Search/SearchList/ListItem/TransactionListItem/index.tsx New dispatcher that chooses the narrow vs wide list-item implementation based on responsive layout.
src/components/Search/SearchList/ListItem/TransactionListItem.tsx Removes the previous combined implementation now replaced by the dispatcher + variants.
src/components/Search/SearchList/ListItem/ActionCell/DeferredActionCell.tsx Defers action button rendering with a skeleton placeholder.

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

Comment on lines +549 to +561
{!shouldShowRadioButton && (
<Checkbox
disabled={isDisabled}
onPress={() => {
onCheckboxPress(transactionItem.transactionID);
}}
accessibilityLabel={CONST.ROLE.CHECKBOX}
isChecked={isSelected}
containerStyle={styles.m0}
wrapperStyle={styles.justifyContentCenter}
sentryLabel={checkboxSentryLabel}
/>
)}
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.

@OlGierd03 I guess this is expected, could you add an explanation comment maybe?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Removed shouldShowCheckbox from TransactionItemRowWideProps via Omit

Comment on lines +302 to +316
case CONST.SEARCH.TABLE_COLUMNS.TO:
return (
<View
key={column}
style={[StyleUtils.getReportTableColumnStyles(CONST.SEARCH.TABLE_COLUMNS.FROM)]}
>
{!!transactionItem.to && (
<UserInfoCell
accountID={transactionItem.to.accountID}
avatar={transactionItem.to.avatar}
displayName={transactionItem.formattedTo ?? transactionItem.to.displayName ?? ''}
isLargeScreenWidth
/>
)}
</View>
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.

Even though TO and FROM both columns resolve to the same style at the end, this suggestion is valid.
@OlGierd03 please make this change.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Updated

styles.flex1,
animatedHighlightStyle,
styles.userSelectNone,
isLastItem && [styles.searchTableBottomRadius, styles.overflowHidden, styles.searchTableBottomRadius],
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.

Valid suggestion.
cc. @OlGierd03

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Removed duplicate

Comment on lines +90 to +91
isFirstItem && [styles.searchTableTopRadius, styles.overflowHidden, styles.searchTableTopRadius],
isLastItem && [styles.searchTableBottomRadius, styles.overflowHidden, styles.searchTableBottomRadius],
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Removed duplicate

luacmartins
luacmartins previously approved these changes May 12, 2026
Copy link
Copy Markdown
Contributor

@luacmartins luacmartins left a comment

Choose a reason for hiding this comment

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

LGTM

@ChavdaSachin
Copy link
Copy Markdown
Contributor

Reviewing ♻️

@ChavdaSachin
Copy link
Copy Markdown
Contributor

ChavdaSachin commented May 12, 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 Screenshot 2026-05-12 at 8 18 38 PM
Android: mWeb Chrome
iOS: HybridApp Screenshot 2026-05-12 at 8 10 35 PM
iOS: mWeb Safari
MacOS: Chrome / Safari Screenshot 2026-05-12 at 8 10 26 PM

Copy link
Copy Markdown
Contributor

@ChavdaSachin ChavdaSachin left a comment

Choose a reason for hiding this comment

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

LGTM! ✅

Ps. Please wait for the author to remove the duplicate changes before merging.

@melvin-bot melvin-bot Bot requested a review from luacmartins May 12, 2026 14:58
@luacmartins
Copy link
Copy Markdown
Contributor

@OlGierd03 can you please address the co-pilot comments?

@jmusial
Copy link
Copy Markdown
Contributor Author

jmusial commented May 12, 2026

@luacmartins addressed

@luacmartins
Copy link
Copy Markdown
Contributor

@jmusial performance test is failing

@jmusial
Copy link
Copy Markdown
Contributor Author

jmusial commented May 13, 2026

@luacmartins all passing now

@luacmartins luacmartins merged commit 70ab5b7 into Expensify:main May 13, 2026
34 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

🚧 @luacmartins 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/luacmartins in version: 9.3.74-0 🚀

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

Bundle Size Analysis (Sentry):

@MelvinBot
Copy link
Copy Markdown
Contributor

No help site changes are required for this PR.

This is an internal performance optimization that splits TransactionItemRow and TransactionListItem into viewport-specific variants (Wide/Narrow) and adds deferred-rendering wrappers. There are no user-facing feature changes, new UI labels, or workflow modifications that would need to be reflected in the help site documentation.

@mitarachim
Copy link
Copy Markdown

Deploy Blocker #90587 was identified to be related to this PR.

@OSBotify
Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/Beamanator in version: 9.3.74-7 🚀

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

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.

9 participants