Skip to content

[CFI] Update the Edit multiple flow to use inline editing and dropdown down style rows - #106067

Open
DylanDylann wants to merge 18 commits into
Expensify:mainfrom
DylanDylann:dylann/101571-edit-multiple-inline-fields
Open

DylanDylann wants to merge 18 commits into
Expensify:mainfrom
DylanDylann:dylann/101571-edit-multiple-inline-fields

Conversation

@DylanDylann

@DylanDylann DylanDylann commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

Fixed Issues

$ #101571
PROPOSAL:

Tests

Same as QA steps

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

Precondition: a workspace with categories, tags, tax tracking and attendee tracking enabled, and at least three expenses submitted to it. Go to Reports > Expenses, select two or more of those expenses and choose Edit multiple.

  1. Verify Amount, Description, Merchant and Date render as inline inputs, and Category, Tag, Tax rate, Billable, Reimbursable and Attendees render as bordered rows with a down caret.
  2. Verify the Amount input shows the workspace currency symbol as a prefix and the currency code at the end of the row.
  3. Type an amount, a description and a merchant, and pick a date. Press Save. Verify every selected expense gets those values.
  4. Open Edit multiple again. Press the currency code on the Amount row. Verify the currency picker opens. Pick another currency and verify the symbol and code on the row update. Type an amount and press Save. Verify every selected expense gets that amount in the picked currency.
  5. Open Edit multiple again. Type (none) as the merchant. Verify an error shows under the field and Save does nothing. Clear the field and verify the error goes away.
  6. Type a description longer than the description limit. Verify an error shows under the field and Save does nothing.
  7. Select expenses that include an IOU (P2P) expense. Type 0 as the amount. Verify an error shows under the field and Save does nothing.
  8. Select expenses that include a distance expense. Verify Merchant renders as a locked field, not an input.
  9. On a touch device, select expenses whose reports all allow negative amounts. Verify the Amount row shows Flip. Press it and verify the amount sign flips. Select expenses on an IOU report and verify Flip is gone.
  10. Press Category. Verify the list opens anchored below the row (a bottom sheet on narrow screens). Pick a category and verify the row shows it. Press the row again and pick the same category. Verify the row clears.
  11. Repeat step 10 for Tag and Tax rate.
  12. Press Attendees. Verify the attendee list opens anchored to the row with a search field and an Apply button. Pick attendees and press Apply. Verify the row shows them. Open again, change the selection and dismiss without Apply. Verify the row keeps the applied selection.
  13. Press Reimbursable and Billable. Verify the list shows Don’t change picked by default, then pick No. Save and verify every expense is marked non-reimbursable and non-billable. Reopen, leave it on Don’t change, save and verify the expenses keep their own values
  14. Save with category, tag, tax rate, billable and attendees picked. Verify every selected expense gets them.
  • 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 verified any copy / text that was added to the app 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 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 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 the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • 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-11-05.at.17.03.57.mov
Android: mWeb Chrome
Screen.Recording.2026-11-05.at.17.01.19.mov
iOS: Native
Screen.Recording.2026-11-05.at.16.45.45.mov
iOS: mWeb Safari
Screen.Recording.2026-11-05.at.16.54.39.mov
MacOS: Chrome / Safari
Screen.Recording.2026-11-05.at.16.44.34.mov

@DylanDylann
DylanDylann requested review from a team as code owners November 5, 2026 07:45
@melvin-bot
melvin-bot Bot requested review from ikevin127 and removed request for a team November 5, 2026 07:45
@melvin-bot

melvin-bot Bot commented Nov 5, 2026

Copy link
Copy Markdown

@ikevin127 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 requested review from JmillsExpensify and removed request for a team November 5, 2026 07:45
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 5, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ⚠️ Failed 2026-11-05T09:38:48.661509Z
We couldn’t complete this review. Comment @codex review to try again.
de9bd92 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@ikevin127

ikevin127 commented Nov 5, 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 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
    • 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
    • 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 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 the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • 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

Screen.Recording.2026-11-05.at.16.49.39.mov

@DylanDylann
DylanDylann marked this pull request as draft November 5, 2026 08:47
@codecov

codecov Bot commented Nov 5, 2026 •

Copy link
Copy Markdown

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 Δ
src/CONST/SENTRY_LABEL.ts 100.00% <ø> (ø)
src/ONYXKEYS.ts 100.00% <ø> (ø)
src/ROUTES.ts 34.33% <ø> (ø)
src/SCREENS.ts 100.00% <ø> (ø)
...AmountActionButtons/AmountCurrencyPickerButton.tsx 94.44% <100.00%> (+1.11%) ⬆️
...nents/AmountActionButtons/AmountSignFlipButton.tsx 100.00% <100.00%> (ø)
.../components/AttendeePicker/AttendeePickerModal.tsx 100.00% <100.00%> (ø)
...eyRequestConfirmationList/sections/AmountField.tsx 86.59% <ø> (-0.19%) ⬇️
src/components/TaxPicker/TaxPickerModal.tsx 100.00% <100.00%> (ø)
...gation/AppNavigator/ModalStackNavigators/index.tsx 7.79% <ø> (+0.04%) ⬆️
... and 13 more
... and 12 files with indirect coverage changes

…dit multiple functionality, replacing them with toggle options in the main edit page.
@DylanDylann
DylanDylann marked this pull request as ready for review November 5, 2026 09:20
@DylanDylann

Copy link
Copy Markdown
Contributor Author

@shawnborton @JmillsExpensify I’d suggest letting users type “-” in the amount input as we do in the creation flow, instead of adding a new icon at the end of the row as shown in the mockup. What do you think?

My Change
Screenshot 2026-11-05 at 16 20 43

Design
Screenshot 2026-11-05 at 16 21 37

Comment thread src/libs/MoneyRequestUtils.ts Resolved
@shawnborton

Copy link
Copy Markdown
Contributor

I’d suggest letting users type “-” in the amount input as we do in the creation flow, instead of adding a new icon at the end of the row as shown in the mockup. What do you think?

That makes sense, I think we only need the Flip button on mobile devices.

@DylanDylann

This comment was marked as outdated.

@DylanDylann

Copy link
Copy Markdown
Contributor Author

@ikevin127 Ready for review

@JmillsExpensify JmillsExpensify 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.

Agree with the above. All LGTM

@ikevin127 ikevin127 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.

Requesting changes for two blockers: the amount saves without the currency the row shows, and switching a toggle on and then off writes false to every selected expense.

Comment thread tests/ui/SearchEditMultiplePageTest.tsx Resolved

Copy link
Copy Markdown
Contributor

Looks like this'll be ready for another review soon?

@shawnborton

Copy link
Copy Markdown
Contributor

I see some commits so I'll run another test build.

@github-actions

Copy link
Copy Markdown
Contributor

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

@github-actions

Copy link
Copy Markdown
Contributor

@shawnborton

Copy link
Copy Markdown
Contributor

For tags, I don't think we need to repeat the field label above the popover. We only do that for mobile when we launch the popover from the bottom using the bottom-docked pattern:
CleanShot 2026-11-10 at 11 45 22 AM@2x

@shawnborton

Copy link
Copy Markdown
Contributor

On that note, I thought we decided that for mobile inline popovers, all of them should have the small back arrow and heading title like this?
CleanShot 2026-11-10 at 11 46 06 AM@2x

cc @trjExpensify for confirmation there

@trjExpensify

Copy link
Copy Markdown
Contributor

cc @trjExpensify for confirmation there

Correct. 👍

@ikevin127 ikevin127 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.

Request changes with blockers. Resolved the thread, but saveDraftReimbursable and saveDraftBillable still write isOn straight to the draft, so switching a toggle on then off still sends false to every selected expense. The QA steps also still describe Billable and Reimbursable as dropdown rows, and they are toggles now.

@DylanDylann

Copy link
Copy Markdown
Contributor Author

For tags, I don't think we need to repeat the field label above the popover. We only do that for mobile when we launch the popover from the bottom using the bottom-docked pattern:

For this, I’d prefer to keep it as is so it stays consistent between the creation flow and the edit details flow. If we agree to change it, I suggest doing it in a separate PR that fixes it everywhere

@DylanDylann DylanDylann mentioned this pull request Nov 11, 2026
38 tasks done
@DylanDylann

Copy link
Copy Markdown
Contributor Author

@shawnborton @ikevin127 Updated the reimbursable toggle

Screenshot 2026-11-11 at 16 50 31 Screenshot 2026-11-11 at 16 49 02

@shawnborton

Copy link
Copy Markdown
Contributor

If Don't change is selected, shouldn't that be reflected in the input itself? I don't see a value under the label.

…earchEditMultiplePage to integrate AmountFormField. Add tests for borderless button behavior.
@DylanDylann

Copy link
Copy Markdown
Contributor Author

The failed check on main

@trjExpensify

Copy link
Copy Markdown
Contributor

If Don't change is selected, shouldn't that be reflected in the input itself? I don't see a value under the label.

What is this "Don't change" thing? I don't see it on prod. I even selected one non-reimbursable expense and one reimbursable expense. 🤔

image

@ikevin127 ikevin127 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.

🟢 LGTM - Approved. The currency and the on/off toggle problems are both fixed. Before merge, please fill in the empty Explanation of Change and add a QA step for the new Billable and Reimbursable Don’t change / Yes / No list.

  • QA step 1 matches the new rows. Step 13 mentions billable but never says how to pick a value.
    • Suggested wording: "Press Reimbursable and Billable. Verify the list shows Don’t change picked by default, then pick No. Save and verify every expense is marked non-reimbursable and non-billable. Reopen, leave it on Don’t change, save and verify the expenses keep their own values."
    • QA runs steps verbatim, so this one is worth adding.

cc @DylanDylann

@melvin-bot
melvin-bot Bot requested a review from puneetlath November 11, 2026 23:50
@DylanDylann

Copy link
Copy Markdown
Contributor Author

@trjExpensify On production, you can click a selected option again to deselect it. When no option is selected, the expenses keep their previous value. That’s what “Don’t change” means.

@trjExpensify

Copy link
Copy Markdown
Contributor

@DylanDylann

Copy link
Copy Markdown
Contributor Author

@trjExpensify Got it. Updated

Screen.Recording.2026-11-13.at.13.50.12.mov

This branch has not been deployed

No deployments
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