Skip to content

Migrate ComposedButton to ButtonWithDropdownMenu#93789

Merged
mountiny merged 26 commits into
Expensify:mainfrom
software-mansion-labs:Guccio163/button/ButtonWithDropdownMenu
Jul 6, 2026
Merged

Migrate ComposedButton to ButtonWithDropdownMenu#93789
mountiny merged 26 commits into
Expensify:mainfrom
software-mansion-labs:Guccio163/button/ButtonWithDropdownMenu

Conversation

@Guccio163

@Guccio163 Guccio163 commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

This PR is a part of ButtonComposed migration, implementing the new composed Button from ./ButtonComposed instead of ./Button in the ButtonWithDropdownMenu.

This PR removes ButtonDoubleLineText component, since its only potential usage was inside the ButtonWithDropdownMenu and we can simply use it inline. It also removes the ButtonWithIcons - Button wrapper which is no longer needed, since all of the icon+text coupling logic is gone/implemented inline in designated places.

Fixed Issues

$ #83762
PROPOSAL:

Tests

ButtonWithDropdownMenu can include icons, text and second-line text. Below are test steps for 3 UI
variants of ButtonWithDropdownMenu, verify that all of them are correct. Correctness means the button
is identical to the current one (main/staging/prod); subtle changes like the gap between the text and
icon are also intentional.

All three variants are reached via the report-header pay button (SettlementButton), which is the only
place in the app that renders every form (single, split-with-arrow, and double-line).


Variant 1: "Mark as paid" (single button — text only, NO icon, NO dropdown arrow)

What we're testing: BWDM as a single button — just Button.Text ("Mark as paid"). No leading icon
(SettlementButton doesn't pass an icon), no dropdown arrow, no second line.

Steps (needs a second test account, "User B"):

  1. Sign in as User A and open (or start) a 1:1 DM with User B.
  2. As User B, in that DM submit an expense / request money from User A using a currency that is NOT
    USD/AUD/CAD/GBP/EUR — e.g. PLN, amount e.g. 50. (Set the currency on the amount screen before
    creating.) This makes User A the payer on the resulting IOU.
  3. Back as User A, open the IOU report from that DM.
  4. In the header you'll see a single button "Mark as paid", NO icon and NO dropdown arrow.

Variant 2: "Pay $XX" (split button — dropdown arrow visible, single-line label)

What we're testing: BWDM as a split button — text + dropdown-arrow icon, no subtitle.

Steps:

  1. Onboard a new account choosing "Manage my team's expenses" (a Collect group workspace is
    auto-created). Keep the workspace currency as USD.
  2. Go to Workspaces → [workspace] → More features → enable Workflows.
  3. Open Workflows and turn the "Payments" toggle ON. If it prompts to connect a bank account,
    CLOSE / skip it — do NOT connect an account.
  4. In the workspace chat, tap Expense in the quick actions → enter an amount (e.g. 50) → add a merchant
    → Create expense.
  5. Open Spend → Reports, hit Submit, then hit Approve on the row.
  6. Open the report. The header shows a green split button "Pay $50.00" with a dropdown arrow on the right.
  7. Tap the arrow — the menu contains "Business bank account" (starts the connect-bank flow) and
    "Pay elsewhere".
  8. The primary button label is a single line — just "Pay $50.00", no subtitle.

Variant 3: "Pay $XX" + second-line text (split button WITH subtitle / double-line)

What we're testing: BWDM with double-line text — line 1 amount, line 2 payment-method subtitle. This is the only path in the app that produces secondLineText (SettlementButton).

Steps:

  1. Start from the Variant 2 workspace (Payments ON).
  2. Open Workflows → in the "Payments" section tap the empty payment-account row / "Connect bank account" and complete the business bank account (VBBA) setup flow to a verified (OPEN) account. On dev the magic code is 000000. When done, the "Payments" section shows "Bank account ending in XXXX".
  3. Create another expense → Submit → Approve.
  4. Open the new report. The Pay button now reads:
    • line 1: "Pay $50.00"
    • line 2: "Bank account ending in XXXX"

Note: the old "enable Wallet → Wallet subtitle" path does NOT apply to expense reports (wallet payment
is only offered on P2P/invoice reports), so the expense-report subtitle comes from the connected VBBA.

Pragmatic alternative (if KYC/bank setup is too slow): import the prepared Onyx state

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

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
Screen.Recording.2026-06-18.at.17.45.27.mov
Screen.Recording.2026-06-18.at.18.00.30.mov
Screen.Recording.2026-06-18.at.18.00.59.mov
Android: mWeb Chrome
Screen.Recording.2026-06-18.at.17.48.56.mov
Screen.Recording.2026-06-18.at.17.57.48.mov
Screen.Recording.2026-06-18.at.17.59.10.mov
iOS: Native
Screen.Recording.2026-06-18.at.18.07.00.mov
Screen.Recording.2026-06-18.at.18.07.34.mov
Screen.Recording.2026-06-18.at.17.15.59.mov
iOS: mWeb Safari
Screen.Recording.2026-06-18.at.18.11.51.mov
Screen.Recording.2026-06-18.at.18.12.14.mov
Screen.Recording.2026-06-18.at.17.22.25.mov
MacOS: Chrome / Safari
Screen.Recording.2026-06-18.at.19.09.36.mov
Screen.Recording.2026-06-18.at.19.10.39.mov
Screen.Recording.2026-06-18.at.13.20.54.mov

@Guccio163 Guccio163 changed the title Guccio163/button/button with dropdown menu Migrate ComposedButton to ButtonWithDropdownMenu Jun 17, 2026
@codecov

codecov Bot commented Jun 19, 2026

Copy link
Copy Markdown

@Guccio163 Guccio163 marked this pull request as ready for review June 19, 2026 05:57
@Guccio163 Guccio163 requested review from a team as code owners June 19, 2026 05:57
@melvin-bot melvin-bot Bot requested review from ZhenjaHorbach and joekaufmanexpensify and removed request for a team June 19, 2026 05:57
@melvin-bot

melvin-bot Bot commented Jun 19, 2026

Copy link
Copy Markdown

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

@melvin-bot melvin-bot Bot removed the request for review from a team June 19, 2026 05:57
Comment thread src/components/ButtonComposed/index.tsx
Comment thread src/components/ButtonWithDropdownMenu/index.tsx Outdated
@ZhenjaHorbach

ZhenjaHorbach commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

Oh
Big PR 😁
Will start today or on Monday!

@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

No product review needed

@joekaufmanexpensify joekaufmanexpensify removed their request for review June 22, 2026 21:30
@ZhenjaHorbach

ZhenjaHorbach commented Jun 24, 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: mWeb Chrome
iOS: HybridApp
2026-07-02.14.18.56.mov
2026-07-02.14.19.12.mov
2026-07-02.14.19.39.mov
2026-07-02.14.21.54.mov
2026-07-02.14.22.20.mov
2026-07-02.14.23.01.mov
2026-07-02.14.24.38.mov
2026-07-02.14.27.28.mov
2026-07-02.14.28.34.mov
2026-07-02.14.29.23.mov
iOS: mWeb Safari
2026-07-02.13.27.39.mov
2026-07-02.13.30.53.mov
2026-07-02.13.39.36.mov
2026-07-02.13.40.23.mov
2026-07-02.13.41.47.mov
2026-07-02.13.44.17.mov
2026-07-02.13.44.58.mov
2026-07-02.14.04.06.mov
2026-07-02.14.04.58.mov
MacOS: Chrome / Safari
2026-07-02.12.06.56.mov
2026-07-02.12.07.25.mov
2026-07-02.12.08.10.mov
2026-07-02.12.18.39.mov
2026-07-02.12.20.46.mov
2026-07-02.12.21.38.mov
2026-07-02.12.22.19.mov
2026-07-02.12.23.21.mov
2026-07-02.12.27.45.mov

@Guccio163

Copy link
Copy Markdown
Contributor Author

I also restored the ButtonProps barrel export, just a sidenote; @ZhenjaHorbach I think all checks are passing, so we can also check this one ✅

@ZhenjaHorbach

Copy link
Copy Markdown
Contributor

From my side everything is good!

@ZhenjaHorbach

Copy link
Copy Markdown
Contributor

@codex
Review this PR

@ZhenjaHorbach

Copy link
Copy Markdown
Contributor

@MelvinBot
Review this PR

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 PR Review — mostly a clean mechanical migration, but there's one behavior change worth confirming before merge.

⚠️ Main concern: mobile search Pay button loses its extra-small size

The new composed Button only supports BUTTON_SIZE (SMALL/MEDIUM/LARGE) — there is no EXTRA_SMALL (CONST/index.ts), whereas the old DROPDOWN_BUTTON_SIZE did. As part of this migration, PayActionCell.tsx:158 dropped extraSmall ? EXTRA_SMALL : SMALL and now hardcodes SMALL.

Extra-small is a genuinely smaller button (minHeight: componentSizeXSmall, paddingHorizontal: 8, fontSizeExtraSmall) vs small (componentSizeSmall, 12, fontSizeSmall). So on narrow/mobile screens (extraSmall was !isLargeScreenWidth), the Pay button in Search list rows will now render taller with larger text/padding. This is a visible UI change that isn't mentioned in the description and isn't covered by the test steps (which only exercise the report-header "Mark as paid"/"Pay" variants, not the Search list ActionCell on a small screen).

Please confirm with @Expensify/design that dropping extra-small here is intended, or preserve the smaller size on narrow screens.

Dead extraSmall props left behind

With extra-small gone, the extraSmall prop is now inert everywhere — SettlementButton still forwards it (types.ts:78, index.tsx:694) to ButtonWithDropdownMenu, which still declares it (types.ts:95) but no longer reads it. Recommend removing these to avoid a misleading no-op prop (tied to the decision above).

Minor

  • The inline DoubleLineButtonText adds styles.ph1 to the second-line Text, which the removed ButtonDoubleLineText didn't have. Your description notes some gap tweaks are intentional — just flagging so it's a conscious choice on the second line.

Looks good

  • Removals are clean — no orphaned references to ButtonDoubleLineText, ButtonWithIcons, or Button.DoubleLineText anywhere in src/tests.
  • Relocating withNavigationFallback from the whole Button to only ButtonKeyboardShortcut is correct: ButtonComposed/Button.tsx uses no navigation hooks, so only the keyboard-shortcut path needs the fallback context.
  • The remaining CONST.BUTTON_SIZEDROPDOWN_BUTTON_SIZE value strings are identical ('medium'/'small'/'large'), so the size prop swap is behavior-preserving for those three.
  • Composed-button test import updated to the barrel export.
Note on verification

This is a static review of the diff against the branch head (c5ec0e5). I did not run typecheck/lint/tests or exercise the UI, so please rely on CI + your manual test matrix for the runtime checks — especially a Search-list Pay button screenshot on a narrow screen to gauge the size change above.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. You're on a roll.

Reviewed commit: c5ec0e5ac0

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

@ZhenjaHorbach

Copy link
Copy Markdown
Contributor

As I remeber we decided to remove extraSmall a bit later

@Guccio163

Guccio163 commented Jul 6, 2026

Copy link
Copy Markdown
Contributor Author

Exactly, moreover extra-small wasn't even really used, so this change isn't visible anywhere; Looks like the rest is clean then ✨

@melvin-bot melvin-bot Bot requested a review from mountiny July 6, 2026 12:21

@mountiny mountiny left a comment

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.

Just NAB comments

Comment on lines +36 to +40
type DoubleLineButtonTextProps = {
primaryText: string;
primaryTextStyle?: StyleProp<TextStyle>;
secondLineText: string;
};

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.

docs

stayNormalOnDisable={shouldStayNormalOnDisable}
isLoading={isLoading}
shouldRemoveRightBorderRadius
removeBorderRadius="right"

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.

Is there no const for this?

<Button
success={success}
pressOnEnter={pressOnEnter}
variant={success ? 'success' : undefined}

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.

no const for the success variant?

@mountiny mountiny merged commit bb6e72c into Expensify:main Jul 6, 2026
36 checks passed
@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

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

@OSBotify

OSBotify commented Jul 6, 2026

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.

@Guccio163

Copy link
Copy Markdown
Contributor Author

Right, I'll address the comments in the follow-up; Do you think we should make consts for these two button props? They are already type-guarded for only the allowed options, but if you prefer I can also change this into consts, just LMKWYT @mountiny

@mountiny

mountiny commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

I feel like the consts make it a bit cleaner if the value is reused somewhere

@Guccio163

Copy link
Copy Markdown
Contributor Author

It sure does; I wasn't sure if we want to add more consts just for this one component, but surely those ~300 calls should be enough to introduce them 😆

@OSBotify

OSBotify commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/mountiny in version: 9.4.28-0 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 Help site review — no changes required.

I reviewed this PR's changes against Expensify's help site content under App/docs/articles and no documentation updates are needed, so I did not create a draft help site PR.

Why: This is a purely internal component refactor with no user-facing surface that the help site describes:

  • It migrates ButtonWithDropdownMenu to the composed Button and swaps CONST.DROPDOWN_BUTTON_SIZECONST.BUTTON_SIZE.
  • It removes internal-only components (ButtonDoubleLineText, ButtonWithIcons) and reorganizes primitives.
  • There are no new/renamed features, tabs, settings labels, or buttons, and no src/languages/* copy changes — the button labels ("Pay", "Mark as paid", "More", etc.) are unchanged; only the underlying implementation changed.

Help articles document product features and flows (how to pay/approve reports, workspace settings, etc.), none of which change here. The one behavioral nuance I flagged in my code review (Search-list Pay button losing its extra-small size on narrow screens) is a visual sizing detail that isn't covered by any help article, so it needs no docs update regardless of how that's resolved.

If a reviewer believes a specific article is affected, reply with the article path and I'll draft the update.

@lanitochka17

lanitochka17 commented Jul 6, 2026

Copy link
Copy Markdown

Hello @ZhenjaHorbach @Guccio163
How can we find Reimbursement and pick "Manual" (instead of Direct)?

Cuplikan layar 2026-07-07 015954

@Guccio163

Copy link
Copy Markdown
Contributor Author

Sorry @lanitochka17, those test steps were outdated, I just updated them so should be fine ✔️

@OSBotify

OSBotify commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 9.4.28-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.

7 participants