Skip to content

Update the policy expensify card table to the new style#94860

Merged
luacmartins merged 4 commits into
mainfrom
revert-94807-revert-93861-cmartins-ecardTable
Jun 29, 2026
Merged

Update the policy expensify card table to the new style#94860
luacmartins merged 4 commits into
mainfrom
revert-94807-revert-93861-cmartins-ecardTable

Conversation

@luacmartins

@luacmartins luacmartins commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Migrate the policy Expensify Card list page to the shared Table component.

Render the frozen card status below the row (matching the Spend table violation pattern) so long admin names no longer wrap into adjacent columns.

Fixed Issues

$ #86212
$ #94750

Tests

  1. Open a workspace Expensify Card page with issued cards
  2. Confirm balance, remaining limit, and cash back labels render above the table
  3. Confirm cardholder, type, limit type, last four, and limit columns render on wide screens
  4. Tap a row → card details opens
  5. Select multiple cards and confirm bulk Export as CSV still works
  6. With 12+ cards, confirm search and sorting work
  7. Confirm Issue card, Settings, and feed selector still work
  8. Click on a card row
  9. Freeze card
  10. With a frozen card (especially frozen by an admin with a long email display name), confirm the frozen message renders on one line below the row and does not overlap adjacent columns
  • Verify that no errors appear in the JS console
Screenshot 2026-06-17 at 3 56 39 PM Screenshot 2026-06-17 at 3 56 56 PM Screenshot 2026-06-29 at 9 19 56 AM Screenshot 2026-06-29 at 9 20 09 AM

Offline tests

N/A

QA Steps

Same as tests

  • Verify that no errors appear in the JS console

@luacmartins luacmartins self-assigned this Jun 29, 2026
Move the frozen card status below the row grid (matching the pre-table layout and Spend table violation pattern) so long admin names no longer wrap into adjacent columns.
@luacmartins luacmartins marked this pull request as ready for review June 29, 2026 15:20
@luacmartins luacmartins requested review from a team as code owners June 29, 2026 15:20
@melvin-bot melvin-bot Bot requested review from JmillsExpensify, Krishna2323 and situchan and removed request for a team June 29, 2026 15:20
@melvin-bot

melvin-bot Bot commented Jun 29, 2026

Copy link
Copy Markdown

@Krishna2323 @situchan One of you needs to 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]

@codecov

codecov Bot commented Jun 29, 2026

Copy link
Copy Markdown

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/CONST/index.ts 94.07% <ø> (ø)
src/components/Table/TableBody.tsx 96.55% <100.00%> (+0.55%) ⬆️
src/components/Table/TableRow.tsx 75.00% <ø> (ø)
...e/expensifyCard/WorkspaceExpensifyCardListPage.tsx 0.00% <0.00%> (ø)
...sifyCardsTable/WorkspaceExpensifyCardsTableRow.tsx 0.00% <0.00%> (ø)
...ents/Tables/WorkspaceExpensifyCardsTable/index.tsx 0.00% <0.00%> (ø)
... and 24 files with indirect coverage changes

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

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: 23e1171a4c

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/components/Table/TableRow.tsx
const limitTypeLabel = translate(getTranslationKeyForLimitType(item.limitType));
const formattedLimit = convertToShortDisplayString(item.limit, item.currency);
const formattedFrozenDate = item.frozenDate ? DateUtils.formatWithUTCTimeZone(item.frozenDate, CONST.DATE.MONTH_DAY_YEAR_ABBR_FORMAT) : '';
const frozenByAdminPrefix = translate('cardPage.frozenByAdminPrefix', {date: formattedFrozenDate});

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.

❌ PERF-2 (docs)

frozenByAdminPrefix calls translate('cardPage.frozenByAdminPrefix', ...) unconditionally for every rendered card row, but the value is only ever used inside the if (formattedFrozenDate) block below. For the common case (a non-frozen card, where formattedFrozenDate is empty) this performs a wasted translate lookup on every row.

Move the translate call inside the guard so it only runs when the card is actually frozen:

let frozenByText: string | undefined;
if (formattedFrozenDate) {
    if (item.frozenByAccountID === session?.accountID) {
        frozenByText = translate('cardPage.youFroze', {date: formattedFrozenDate});
    } else {
        const frozenByAdminPrefix = translate('cardPage.frozenByAdminPrefix', {date: formattedFrozenDate});
        frozenByText = `${frozenByAdminPrefix}${item.frozenByDisplayName ?? translate('common.someone')}`;
    }
}

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

@situchan

Copy link
Copy Markdown
Contributor

How to freeze card?

@luacmartins

Copy link
Copy Markdown
Contributor Author

@situchan you can click on a card row > Freeze card

Screen.Recording.2026-06-29.at.9.43.08.AM.mov

@situchan

Copy link
Copy Markdown
Contributor

Gotcha. Only available on virtual card. Was testing on physical card

@situchan

situchan commented Jun 29, 2026

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

Android: HybridApp
android.mov
android.mov
Android: mWeb Chrome
iOS: HybridApp
ios.mov
ios.mov
iOS: mWeb Safari
MacOS: Chrome / Safari
web.mov
web.mov

Avoids unnecessary translate lookups on non-frozen card rows.
@melvin-bot melvin-bot Bot requested a review from tylerkaraszewski June 29, 2026 15:49
@melvin-bot

melvin-bot Bot commented Jun 29, 2026

Copy link
Copy Markdown

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

@luacmartins luacmartins requested review from JS00001 and removed request for tylerkaraszewski June 29, 2026 15:50
@luacmartins luacmartins merged commit 6c7f410 into main Jun 29, 2026
38 checks passed
@luacmartins luacmartins deleted the revert-94807-revert-93861-cmartins-ecardTable branch June 29, 2026 16:15
@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.4.25-0 🚀

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

@jponikarchuk

Copy link
Copy Markdown

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

@OSBotify

OSBotify commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/cristipaval in version: 9.4.25-2 🚀

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