`MenuItemWithTopDescription` decomposition - simplest usages by war-in · Pull Request #100191 · Expensify/App

war-in · 2026-09-02T15:13:13Z

Explanation of Change

Phase 3 of the MenuItem decomposition:

Split the text leaves into Title, Description, FieldName, FieldNamePlaceholder and FieldValue, over two shared bases (BaseMenuItemPrimaryText, BaseMenuItemSupportingText).
Keyed the accessibility slots by line (top/bottom) instead of role, so the announced order matches the visual one for both field and navigation rows.
Replaced MenuItemEmptyField with a MenuItemField preset that renders both the filled (name + value) and empty (name only) shapes.
Migrated ~107 MenuItemWithTopDescription call sites across 55 screens to MenuItemField.
Added a Phase 3 section to the MenuItemComparison story, one card per prop shape.

Fixed Issues

$ #100312
PROPOSAL:

Tests

Open Storybook (npm run storybook) and go to the MenuItem Comparison story.
Scroll to the Phase 3 — MenuItemWithTopDescription section.
Verify that for every card the legacy MenuItemWithTopDescription column, the composable column, and the preset column render identically — same font size, weight, line height, spacing, chevron placement, and truncation.
Filled field rows: navigate to Settings > Profile > (a chat) > Notification preferences row, Workspace > Categories > (a category) settings, Workspace > Tags > (a tag) settings, Workspace > Members > (a member) details, and Workspace > Per diem > (a rate) details.
Verify that each row shows the small grey field name on the top line and the full-contrast value below it, with a chevron when the row is pressable.
Tap the rows and verify navigation still works, and that non-interactive rows (e.g. Travel > Trip details > Car type) show no chevron and do not respond to taps.
Empty field rows: go to Settings > Preferences > Vacation delegate with no delegate set, and Workspace > Company cards > Assign card > Confirmation with an unfilled field.
Verify that the field name renders at normal (not small) font size and takes over the row, with the chevron on the right.
Turn on VoiceOver (iOS) / TalkBack (Android) and focus one filled row and one empty row.
Verify that the row is announced as a single element reading the top line first then the bottom line (e.g. "Notification preferences, Daily"), and the empty row announces just the field name.

Offline tests

N/A — presentational refactor only; no API calls or Onyx writes were changed.

QA Steps

Same as tests (steps 4-10; the Storybook step is dev-only).

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

…sages

…-item-with-top-description-decomposition

…-item-with-top-description-decomposition # Conflicts: # src/pages/workspace/expensifyCard/issueNew/ConfirmationStep.tsx

…osition # Conflicts: # src/stories/MenuItemComparison.stories.tsx

…osition # Conflicts: # src/pages/settings/Wallet/InternationalDepositAccount/subPages/Confirmation.tsx

codecov · 2026-09-03T12:09:37Z

Codecov Report

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

Files with missing lines	Coverage Δ
...mponents/MenuItem/MenuItemAccessibilityContext.tsx	`74.35% <100.00%> (ø)`
src/components/MenuItem/index.ts	`100.00% <ø> (ø)`
...ts/MenuItem/leaves/content/MenuItemDescription.tsx	`100.00% <100.00%> (ø)`
...ents/MenuItem/leaves/content/MenuItemFieldName.tsx	`100.00% <100.00%> (ø)`
...em/leaves/content/MenuItemFieldNamePlaceholder.tsx	`100.00% <100.00%> (ø)`
...nts/MenuItem/leaves/content/MenuItemFieldValue.tsx	`100.00% <100.00%> (ø)`
...mponents/MenuItem/leaves/content/MenuItemLabel.tsx	`100.00% <100.00%> (ø)`
...mponents/MenuItem/leaves/content/MenuItemTitle.tsx	`100.00% <100.00%> (ø)`
...em/leaves/content/base/BaseMenuItemPrimaryText.tsx	`100.00% <100.00%> (ø)`
...leaves/content/base/BaseMenuItemSupportingText.tsx	`100.00% <100.00%> (ø)`
... and 60 more
... and 13 files with indirect coverage changes

war-in · 2026-09-03T15:09:26Z

@codex review

@MelvinBot review

chatgpt-codex-connector · 2026-09-03T15:15:31Z

Codex Review: Something went wrong. Try again later by commenting “@codex review”.

An unknown error occurred

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

MelvinBot · 2026-09-03T15:20:08Z

🤖 Code review of the MenuItemWithTopDescription → MenuItemField migration.

The component work is solid: MenuItemField takes Omit<MenuItemRootProps, 'accessibilityLabel'> and destructures every key, so nothing is silently dropped, and collapsing interactive + shouldShowRightIcon into "chevron follows onPress" is correct at all 41/27 call sites I checked. One real bug, plus a few notes.

🔴 Empty-value guards dropped around interpolated `translate()` keys

ConfirmationBusiness.tsx:111 and :125 lost their guards:

-title={values[INCORPORATION_TYPE] ? translate(`businessInfoStep.incorporationType.${values[INCORPORATION_TYPE]}`) : ''}
+value={translate(`businessInfoStep.incorporationType.${values[BUSINESS_INFO_STEP_KEYS.INCORPORATION_TYPE]}` as TranslationPaths)}

values comes from getSubStepValues(...), so these can be ''. With an empty value the key becomes businessInfoStep.incorporationType. / allStates..stateName, which Localize.translate handles by throwing in dev and, on prod/staging, firing Log.alert and rendering the raw key path. The as TranslationPaths cast means typecheck can't catch it.

It also defeats the new empty-field shape this PR adds — value is a non-empty garbage string, so MenuItemField renders the filled shape instead of the placeholder. Restoring the ternary with undefined instead of '' gives you the placeholder for free:

value={values[BUSINESS_INFO_STEP_KEYS.INCORPORATION_TYPE] ? translate(`...${values[...]}` as TranslationPaths) : undefined}

Notes

helperText has no home in the preset. Three sites now hand-roll the same replacement — a wrapping <View> plus <FormHelpMessage isError={false} shouldShowRedDotIndicator={false} style={[styles.mt0, ...]}/> (ConfirmDelegatePage.tsx:93-99, DynamicXeroTravelBillingConfigurationPage.tsx:55-60). Three copies of an identical style array will drift. Worth either a helperText prop on MenuItemField or a shared wrapper before phase 4 adds more.
Chevron/pressability coupling is undocumented. Because the chevron follows onPress, shouldShowRightIcon !== interactive can't be expressed — EnablePayments/.../ConfirmationStep.tsx:57-71 had to drop to raw MenuItem.Root composition for it. The tradeoff looks right, but say so in the preset's JSDoc so the next migrator doesn't rediscover it.
Stale doc on MenuItemRoot. MenuItemRoot.tsx:34-38 still says the label is derived "from registered Title/Description children" — the slots are top/bottom now.
Minor edge: HotelTripDetails.tsx:68-72 guards on !!reservation.roomClass but passes value={reservation.roomClass.trim()}, so a whitespace-only roomClass renders the empty-field placeholder. Guard on the trimmed value.
Dropping rightLabel in CreateReportFieldsPage.tsx:245 is a no-op — legacy MenuItem only renders rightLabel when title is falsy (MenuItem.tsx:1191) and that row has a title. Flagging only so it's a deliberate removal, not an accident.

Housekeeping

typecheck and ESLint check are red, but both fail only on src/hooks/useTransactionInlineEdit.ts (Cannot find name 'originalUseOnyx'), which this PR doesn't touch — pre-existing on main. Merge main to clear them.
### Fixed Issues is still $ / PROPOSAL: with nothing linked, and every Screenshots/Videos section is empty while all five platform checkboxes are checked.

I reviewed this statically and didn't run the app — the accessibility ordering change (slots keyed top/bottom instead of title/description) is the part worth a real VoiceOver/TalkBack pass, since nothing in CI covers it.

view run

…osition

JakubKorytko

LGTM, one dropped label and two small ones

…osition

war-in · 2026-09-08T11:03:12Z

@Pujan92 all yours 😄

Pujan92 · 2026-09-08T14:05:50Z

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: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

Screen.Recording.2026-09-09.at.14.34.16.mov

Screen.Recording.2026-09-09.at.14.25.26.mov

Screen.Recording.2026-09-09.at.14.22.20.mov

Pujan92 · 2026-09-09T08:44:31Z

@war-in let's merge main and fix conflicts

Pujan92 · 2026-09-09T09:16:55Z

+            <MenuItem.Root onPress={!isBankAccountAdded ? handleModifyAccountNumbers : undefined}>
+                <MenuItem.Row>
+                    <MenuItem.Content>
+                        {!!bankName && <MenuItem.FieldName>{bankName}</MenuItem.FieldName>}
+                        <MenuItem.FieldValue>{`${translate('bankAccount.accountEnding')} ${accountNumber.slice(-4)}`}</MenuItem.FieldValue>
+                    </MenuItem.Content>


can't we use MenuItemField here?

MenuItemField requires the title. Here, title can be undefined, so we would have to make the name optional only for this usage, which doesn't seem reasonable

Pujan92 · 2026-09-09T09:23:24Z

Are we good to have 20px gap between MenuItemRow childrens which seems to not present in the legacy?

war-in · 2026-09-09T09:24:54Z

Are we good to have 20px gap between MenuItemRow childrens which seems to not present in the legacy?

Yes! I discussed this with Shawn and he agreed that the icon should have some space around it

…osition # Conflicts: # src/components/MenuItem/index.ts # src/components/MenuItem/leaves/content/base/MenuItemLabel.tsx # src/pages/DynamicReportParticipantDetailsPage.tsx # src/pages/domain/Groups/PreferredWorkspaceToggle.tsx # src/pages/workspace/reports/CreateReportFieldsPage.tsx # src/pages/workspace/reports/ReportFieldsValueSettingsPage.tsx

war-in · 2026-09-09T10:51:49Z

@Pujan92 review addressed

Pujan92

LGTM!

github-actions · 2026-09-09T17:02:13Z

🚧 roryabraham has triggered a test Expensify/App build. You can view the workflow run here.

github-actions · 2026-09-09T17:12:20Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #100191.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-3607634-cb54e06-62cdfc49746b1fcc6509aaaf10ef6fccec8e55c5/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-3607634-cb54e06-fef6f5ea40ac4c648c1bb39ac8471dd68b825060/index.html

Web 🕸️
https://100191.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

OSBotify · 2026-09-09T17:12:53Z

✋ 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 · 2026-09-09T19:44:48Z

🚀 Deployed to staging by https://github.com/roryabraham in version: 9.4.75-0 🚀

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

MelvinBot · 2026-09-09T19:50:01Z

No help site changes required

I reviewed all 78 changed files. Nothing in docs/articles needs updating, so I did not create a draft docs PR.

Why: this is a presentational refactor of the MenuItem component tree. Every call-site change is a mechanical prop rename onto the new MenuItemField preset — description → name, title → value — reusing the same existing translation keys. No feature, flow, label, or setting name changed.

What I checked

No copy changed. Zero files under src/languages/ are touched, and zero files under docs/ are touched. Every name= / value= prop in the diff resolves to a translation key that was already rendering on that row before this PR (for example notificationPreferencesPage.label, workspace.categories.glCode, travel.trainDetails.seat, domain.groups.preferredWorkspace).

Representative call site — src/pages/ProfilePage.tsx:328: the Notification preferences row swaps MenuItemWithTopDescription for MenuItemField, keeping the same key, same onPress route, and same chevron.

The three behavioral notes in the PR body are all invisible to the help site:

Splitting text leaves over BaseMenuItemPrimaryText / BaseMenuItemSupportingText — internal component structure. The PR's own Storybook test asserts the legacy and new columns render identically (same font size, weight, line height, spacing, chevron placement, truncation).
Keying accessibility slots by line (top/bottom) instead of role — changes screen-reader announcement order only. docs/articles documents product features and workflows, not screen-reader output, so there is nothing there to correct.
Replacing MenuItemEmptyField with a MenuItemField preset that renders both shapes — the empty-field row (for example Vacation delegate with none set) still shows the field name at normal size with a chevron, exactly as before.

Affected surfaces are all already documented accurately. The migrated screens include Notification preferences, workspace Categories / Tags / Members / Per diem / Company cards, Vacation delegate, and the accounting integration pages. Since the rendered text and navigation on each of those rows is unchanged, the existing articles still match the live UI.

@war-in, since this refactor introduces no user-facing change, there is no linked help site PR to review. If you disagree — for example if a row's label or behavior did shift in a way I missed — reply with @MelvinBot <details> and I'll draft the docs PR.

IuliiaHerets · 2026-09-09T19:56:30Z

Hey @war-in. Is it an internal PR?

cc @roryabraham @JakubKorytko @Pujan92

war-in · 2026-09-10T08:13:40Z

Hey @war-in. Is it an internal PR?

@IuliiaHerets I'm not sure if I understand, could you clarify?

IuliiaHerets · 2026-09-10T09:10:22Z

@war-in We can follow only steps 4–8. The other steps are out of our scope.

war-in · 2026-09-10T09:17:18Z

@IuliiaHerets That's what I mentioned in the PR description 😄 But can't you test VoiceOver & TalkBack? I added it to the test steps to make sure accessibility works as expected

IuliiaHerets · 2026-09-10T09:38:08Z

@war-in VoiceOver & TalkBack is out of the scope of our work

war-in · 2026-09-10T09:42:24Z

@IuliiaHerets oh, I didn't know that. So I think it's fine to just test 4-8

OSBotify · 2026-09-10T22:31:05Z

🚀 Deployed to production by https://github.com/mountiny in version: 9.4.75-3 🚀

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

Bundle Size Analysis (Sentry):

Android

OSBotify · 2026-09-11T09:19:02Z

🚀 Deployed to production by https://github.com/mountiny in version: 9.4.75-3 🚀

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

Bundle Size Analysis (Sentry):

Android

war-in added 10 commits August 25, 2026 14:06

feat: add basic title style

85331ef

chore: prepare gallery with the simplest MenuItemWithTopDescription u…

324e0c5

…sages

Merge branch 'war-in/menu-item-decomposition-entity' into war-in/menu…

ae95a97

…-item-with-top-description-decomposition

Merge branch 'war-in/menu-item-decomposition-entity' into war-in/menu…

8d91c69

…-item-with-top-description-decomposition

feat: add MenuItemField preset

68adeb9

chore: migrate MenuItemWithTopDescription basic usages

97dbdf7

chore: update sotrybook Phase 3

24672e5

Merge branch 'war-in/menu-item-decomposition-entity' into war-in/menu…

a107059

…-item-with-top-description-decomposition # Conflicts: # src/pages/workspace/expensifyCard/issueNew/ConfirmationStep.tsx

Merge branch 'main' into war-in/menu-item-with-top-description-decomp…

840d245

…osition # Conflicts: # src/stories/MenuItemComparison.stories.tsx

refactor: split variants into two components

cfa7d51

melvin-bot Bot assigned war-in Sep 2, 2026

war-in added 6 commits September 2, 2026 17:21

fix: make onPress optional

f8bac59

refactor: make MenuItemField display empty state

7b6fc93

refactor: rename title to title strong

398e092

refactor: add FieldName and FieldValue leaves

fa85b4b

Merge branch 'main' into war-in/menu-item-with-top-description-decomp…

5b477d1

…osition # Conflicts: # src/pages/settings/Wallet/InternationalDepositAccount/subPages/Confirmation.tsx

refactor: move value to MenuItemField

a6b633a

war-in added 3 commits September 3, 2026 16:15

refactor: migrate migratable MenuItemWithTopDescription

fde619e

chore: improve MenuItemComparison

931d732

chore: improve comments

0b8fbe5

This was referenced Sep 3, 2026

[Due for payment 2026-10-07] MenuItem decomposition Phase 3 — MenuItemWithTopDescription replacement preset #100312

Open

MenuItem — composition over configuration #96202

Open

war-in added 2 commits September 3, 2026 17:31

Merge branch 'main' into war-in/menu-item-with-top-description-decomp…

9bc9742

…osition

fix: don't pass value for empty strings

d799fad

JakubKorytko approved these changes Sep 4, 2026

View reviewed changes

Comment thread src/pages/workspace/reports/CreateReportFieldsPage.tsx Outdated

Comment thread src/pages/settings/Security/AddDelegate/ConfirmDelegatePage.tsx

Comment thread src/components/MenuItem/presets/MenuItemField.tsx

Merge branch 'main' into war-in/menu-item-with-top-description-decomp…

bc17dd6

…osition

Pujan92 reviewed Sep 9, 2026

View reviewed changes

war-in added 2 commits September 9, 2026 11:42

chore: post-merge fixes

91d90b8

Pujan92 approved these changes Sep 9, 2026

View reviewed changes

melvin-bot Bot requested a review from roryabraham September 9, 2026 10:59

war-in mentioned this pull request Sep 9, 2026

MenuItem decomposition Phase 4 — style-prop remnants #100159

Open

roryabraham approved these changes Sep 9, 2026

View reviewed changes

roryabraham merged commit 3607634 into Expensify:main Sep 9, 2026
36 of 39 checks passed

OSBotify mentioned this pull request Sep 9, 2026

Deploy Checklist: New Expensify 2026-09-09 #100739

Closed

83 tasks done

This was referenced Sep 9, 2026

[Due for payment 2026-09-17] Expense - RHP transition animates outside RHP #100770

Closed

[Due for payment 2026-09-17] Expense- On confirm page, Tag row does not highlight when it appears after changing workspace #100771

Closed

Conversation

war-in commented Sep 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

codecov Bot commented Sep 3, 2026 • edited by github-actions Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

war-in commented Sep 3, 2026

Uh oh!

chatgpt-codex-connector Bot commented Sep 3, 2026

Uh oh!

MelvinBot commented Sep 3, 2026

🔴 Empty-value guards dropped around interpolated translate() keys

Notes

Housekeeping

Uh oh!

JakubKorytko left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

war-in commented Sep 8, 2026

Uh oh!

Pujan92 commented Sep 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

Pujan92 commented Sep 9, 2026

Uh oh!

Pujan92 Sep 9, 2026

Choose a reason for hiding this comment

Uh oh!

war-in Sep 9, 2026

Choose a reason for hiding this comment

Uh oh!

Pujan92 commented Sep 9, 2026

Uh oh!

war-in commented Sep 9, 2026

Uh oh!

war-in commented Sep 9, 2026

Uh oh!

Pujan92 left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

github-actions Bot commented Sep 9, 2026

Uh oh!

github-actions Bot commented Sep 9, 2026

Uh oh!

OSBotify commented Sep 9, 2026

Uh oh!

OSBotify commented Sep 9, 2026

Uh oh!

MelvinBot commented Sep 9, 2026

No help site changes required

Uh oh!

IuliiaHerets commented Sep 9, 2026

Uh oh!

war-in commented Sep 10, 2026

Uh oh!

IuliiaHerets commented Sep 10, 2026

Uh oh!

war-in commented Sep 10, 2026

Uh oh!

IuliiaHerets commented Sep 10, 2026

Uh oh!

war-in commented Sep 10, 2026

Uh oh!

OSBotify commented Sep 10, 2026

Uh oh!

war-in commented Sep 2, 2026 •

edited

Loading

codecov Bot commented Sep 3, 2026 •

edited by github-actions Bot

Loading

🔴 Empty-value guards dropped around interpolated `translate()` keys

Pujan92 commented Sep 8, 2026 •

edited

Loading