Skip to content

feat: handle the Distance and Rate fields for splits#82257

Merged
lakchote merged 21 commits intoExpensify:mainfrom
ZhenjaHorbach:handle-distance-and-rate-for-splits
Feb 24, 2026
Merged

feat: handle the Distance and Rate fields for splits#82257
lakchote merged 21 commits intoExpensify:mainfrom
ZhenjaHorbach:handle-distance-and-rate-for-splits

Conversation

@ZhenjaHorbach
Copy link
Contributor

@ZhenjaHorbach ZhenjaHorbach commented Feb 12, 2026

Explanation of Change

Fixed Issues

$ #78891
#82122
#82120
#82119
#82116
#82134

Tests

Preconditions: User is an Expensifail account and admin have a Workspace

  1. Open App
  2. Create a distance expense ( manual or map)
  3. Tap on the expense detail
  4. Tap on the More button
  5. Tap on the Split
  6. Tap on any split item
  7. Verify that the distance and rate field rows should get added to the Edit Splits screen, which can be changed as well
  8. Try to increase or decrease amounts for splits to be more or less than the original, and try to save
  9. Verify that the user can save these splits (Still show the warning in the split table, but allow them to save)
  10. After creating splits, try to press on the distance or rate field on the transaction details screen
  11. Verify that the user can edit the distance rate and distance on individual splits without opening the split table
  • Verify that no errors appear in the JS console

Offline tests

Preconditions: User is an Expensifail account and admin have a Workspace

  1. Open App
  2. Create a distance expense ( manual or map)
  3. Tap on the expense detail
  4. Tap on the More button
  5. Tap on the Split
  6. Tap on any split item
  7. Verify that the distance and rate field rows should get added to the Edit Splits screen, which can be changed as well
  8. Try to increase or decrease amounts for splits to be more or less than the original, and try to save
  9. Verify that the user can save these splits (Still show the warning in the split table, but allow them to save)
  10. After creating splits, try to press on the distance or rate field on the transaction details screen
  11. Verify that the user can edit the distance rate and distance on individual splits without opening the split table

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

Preconditions: User is an Expensifail account and admin have a Workspace

  1. Open App
  2. Create a distance expense ( manual or map)
  3. Tap on the expense detail
  4. Tap on the More button
  5. Tap on the Split
  6. Tap on any split item
  7. Verify that the distance and rate field rows should get added to the Edit Splits screen, which can be changed as well
  8. Try to increase or decrease amounts for splits to be more or less than the original, and try to save
  9. Verify that the user can save these splits (Still show the warning in the split table, but allow them to save)
  10. After creating splits, try to press on the distance or rate field on the transaction details screen
  11. Verify that the user can edit the distance rate and distance on individual splits without opening the split table
  • 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 there are no new alerts related to the canBeMissing param for useOnyx
  • 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
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
2026-01-13.13.21.34.mov

…pr-79099"

This reverts commit e0a6b4e, reversing
changes made to 9df3d2d.
@ZhenjaHorbach ZhenjaHorbach changed the title Revert "Merge pull request #82147 from ZhenjaHorbach/revert-pr-79099" Handle the Distance and Rate fields for splits Feb 12, 2026
@codecov
Copy link

codecov bot commented Feb 12, 2026

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/index.ts 92.43% <ø> (ø)
src/components/MoneyRequestHeader.tsx 0.00% <ø> (ø)
...c/components/ReportActionItem/MoneyRequestView.tsx 0.44% <ø> (+<0.01%) ⬆️
src/hooks/useSelectedTransactionsActions.ts 83.33% <ø> (ø)
src/libs/API/types.ts 100.00% <ø> (ø)
src/pages/iou/SplitExpenseCreateDateRagePage.tsx 0.00% <ø> (ø)
src/components/MoneyReportHeader.tsx 0.00% <0.00%> (ø)
src/libs/ReportSecondaryActionUtils.ts 92.20% <50.00%> (-0.19%) ⬇️
src/pages/Search/SearchPage.tsx 23.21% <0.00%> (-0.10%) ⬇️
.../iou/request/step/IOURequestStepDistanceManual.tsx 0.00% <0.00%> (ø)
... and 11 more
... and 9 files with indirect coverage changes

@github-actions
Copy link
Contributor

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

@github-actions

This comment has been minimized.

@ZhenjaHorbach ZhenjaHorbach changed the title Handle the Distance and Rate fields for splits feat: handle the Distance and Rate fields for splits Feb 18, 2026
@lakchote lakchote requested a review from suneox February 18, 2026 09:47
@ZhenjaHorbach ZhenjaHorbach marked this pull request as ready for review February 18, 2026 09:47
@ZhenjaHorbach ZhenjaHorbach requested review from a team as code owners February 18, 2026 09:47
@melvin-bot melvin-bot bot requested review from joekaufmanexpensify, lakchote and mkhutornyi and removed request for a team February 18, 2026 09:48
@melvin-bot
Copy link

melvin-bot bot commented Feb 18, 2026

@mkhutornyi @lakchote 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]

@melvin-bot melvin-bot bot requested review from a team and dukenv0307 and removed request for a team February 18, 2026 09:48
@melvin-bot
Copy link

melvin-bot bot commented Feb 18, 2026

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

@mitarachim
Copy link

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

@mitarachim
Copy link

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

@mitarachim
Copy link

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

@mitarachim
Copy link

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

@mitarachim
Copy link

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

@jponikarchuk
Copy link

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

@jponikarchuk
Copy link

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

@lanitochka17
Copy link

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

@jponikarchuk
Copy link

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

@lanitochka17
Copy link

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

@lanitochka17
Copy link

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

@mitarachim
Copy link

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

@mitarachim
Copy link

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

@jponikarchuk
Copy link

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/puneetlath in version: 9.3.26-8 🚀

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

const updatedReportAction = shouldBuildOptimisticModifiedExpenseReportAction
? buildOptimisticModifiedExpenseReportAction(transactionThreadReport, transaction, transactionChanges, isFromExpenseReport, policy, updatedTransaction, allowNegative)
: null;
if (!hasPendingWaypoints && !(hasModifiedDistanceRate && isFetchingWaypointsFromServer(transaction)) && updatedReportAction) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Coming from #83500, we had to relax the condition for split transactions to allow the optimistic MODIFIED_EXPENSE to be created even when waypoints are pending.

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.