Skip to content

MenuItem decomposition - simplest usages - #97339

Draft
war-in wants to merge 36 commits into
Expensify:mainfrom
software-mansion-labs:war-in/menu-item-decomposition-part1
Draft

MenuItem decomposition - simplest usages#97339
war-in wants to merge 36 commits into
Expensify:mainfrom
software-mansion-labs:war-in/menu-item-decomposition-part1

Conversation

@war-in

@war-in war-in commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Part 1 of the MenuItem decomposition. Moves the legacy monolith into src/components/MenuItem/ and introduces a compound API (Root/Row/Content/Icon/Title/Description/Trailing/Chevron) sharing interaction state via context, plus a11y-label derivation from Title/Description. Adds a MenuItem.Standard preset and migrates the simplest call sites to it. Legacy default export unchanged.

Legacy isInteractive prop is derived from onPress, so callers should pass undefined when row is not interactive

Fixed Issues

$
PROPOSAL:

Tests

  1. Open Settings → Profile and other pages migrated to MenuItem.Standard (e.g. Profile, Share Code, Two-Factor Auth Enabled, Expensify Card, Workspace tags import).
  2. Verify each row renders correctly: leading icon, title, optional description below, optional trailing chevron.
  3. Tap a row and verify it navigates / fires its action exactly as before.

Offline tests

N/A — pure component refactor, no API or Onyx changes.

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
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari img img_1 img_2

@war-in

war-in commented Jul 29, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@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: 21764ae4a6

ℹ️ 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/MenuItem/layout/MenuItemRoot.tsx
@war-in

war-in commented Jul 29, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@codecov

codecov Bot commented Jul 29, 2026

Copy link
Copy Markdown

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Chef's kiss.

Reviewed commit: b2d21501b4

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

@JakubKorytko JakubKorytko left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

the compound direction is right and the move itself is clean: 97% similarity rename, seatbelt path updated, compliance passes on all 11 new files, and none of the ~45 migrated call sites drop a prop the preset can't express.

Main thing: the anonymous-session guard stopped being the default. Legacy handed it to every caller (MenuItem.tsx:587), now only MenuItem.Standard applies it while the index.ts doc block tells people to compose Root directly. Details on the onPressAction line.

Second: isCompact merges two legacy notions that were deliberately separate. isCompactPopoverItem (MenuItem.tsx:656) and isCompact = viewMode === COMPACT (MenuItem.tsx:658) fed different helpers, and the context only carries one flag, so getMenuItemTextContainerStyle now gets the popover one and minHeight goes 40 to 20 inside a CompactMenuContext. Root also swaps isSmallScreenWidth for shouldUseNarrowLayout, which legacy suppressed a lint rule to avoid.

Third: the a11y label registry. Children pushing text up into parent state costs an extra subtree render per row, leaves accessibilityLabel="" on first paint, and the "render order" the docs promise is really mount order. Legacy computed it synchronously at MenuItem.tsx:669.

Also: 8 of the 10 test files that mock @components/MenuItem still return a bare function, so .Standard is undefined in them. They pass because the migrated rows sit behind conditions those tests don't hit, so it's a part 2 landmine rather than a break now

Comment thread src/components/MenuItem/layout/MenuItemRoot.tsx
Comment thread src/components/MenuItem/layout/MenuItemContent.tsx Outdated
Comment thread src/components/MenuItem/MenuItemAccessibilityContext.tsx Outdated
Comment thread src/components/MenuItem/MenuItemAccessibilityContext.tsx Outdated
Comment thread src/components/MenuItem/MenuItemAccessibilityContext.tsx Outdated
Comment thread src/components/SettlementAccountSelector.tsx Outdated
Comment thread src/styles/variables.ts Outdated
Comment thread tests/unit/ShareCodePageTranslateTest.tsx Outdated
Comment thread tests/unit/ShareCodePageTranslateTest.tsx Outdated
Comment thread tests/unit/pages/settings/EditAgentPageTest.tsx Outdated
@war-in

war-in commented Aug 3, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@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: 2a4c4b7e4c

ℹ️ 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/MenuItem/presets/MenuItemStandard.tsx Outdated
@war-in

war-in commented Aug 3, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. What shall we delve into next?

Reviewed commit: eece2f86e7

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

2 participants