Skip to content

Allow edit input for SplitListItem when there is negative value - #74189

Merged
lakchote merged 47 commits into
Expensify:mainfrom
callstack-internal:fix-63311
Feb 4, 2026
Merged

lakchote merged 47 commits into
Expensify:mainfrom
callstack-internal:fix-63311

Conversation

@kubabutkiewicz

@kubabutkiewicz kubabutkiewicz commented Nov 4, 2025 •

Copy link
Copy Markdown
Contributor

Explanation of Change

Fixed Issues

$ #63311
PROPOSAL:

Tests

  1. Go to workspace chat.
  2. Go to expense report.
  3. Open the negative expense
  4. Click More > Split.
  5. Click on the split input on any individual split.
  6. Verify that you are able to edit the field
    Try to clear or use backspace to delete the amount.
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

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

  • 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
    • MacOS: Desktop
  • 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
MacOS: Desktop

…thSymbolForm and SplitListItem components. Update MoneyRequestUtils to ensure proper toggling of negative amounts and adjust related tests for expected behavior.
@kubabutkiewicz
kubabutkiewicz requested review from a team as code owners November 4, 2025 12:35
@melvin-bot
melvin-bot Bot requested review from JmillsExpensify and ZhenjaHorbach and removed request for a team November 4, 2025 12:35
@melvin-bot

melvin-bot Bot commented Nov 4, 2025

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 November 4, 2025 12:35
[splitItem],
);

const isBottomVisible = !!splitItem.category || !!splitItem.tags?.at(0);

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.

❌ PERF-6

Passing entire splitItem object as a dependency causes the callback to be recreated whenever any property of splitItem changes, even unrelated ones. This defeats the purpose of memoization and can trigger unnecessary re-renders.

Specify individual properties as dependencies instead:

const onSplitExpenseAmountChange = useCallback(
    (amount: string) => {
        splitItem.onSplitExpenseAmountChange(splitItem.transactionID, Number(amount));
    },
    [splitItem.onSplitExpenseAmountChange, splitItem.transactionID],
);

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

Looks good on behalf of product-pr. This is cleaning up the behavior around negative values and splits.

@codecov

codecov Bot commented Nov 4, 2025 •

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/components/AmountTextInput.tsx 100.00% <100.00%> (ø)
src/components/MoneyRequestAmountInput.tsx 1.92% <ø> (ø)
...onList/ListItem/SplitListItem/SplitAmountInput.tsx 0.00% <ø> (ø)
...st/ListItem/SplitListItem/SplitPercentageInput.tsx 0.00% <ø> (ø)
...nput/BaseTextInput/implementation/index.native.tsx 77.72% <100.00%> (+0.10%) ⬆️
...s/TextInput/BaseTextInput/implementation/index.tsx 0.00% <ø> (ø)
...omponents/SelectionList/ListItem/SplitListItem.tsx 0.00% <0.00%> (ø)
src/libs/MoneyRequestUtils.ts 54.76% <87.50%> (+2.13%) ⬆️
src/pages/iou/SplitExpenseEditPage.tsx 0.00% <0.00%> (ø)
src/components/NumberWithSymbolForm.tsx 2.77% <0.00%> (-0.04%) ⬇️
... and 3 more
... and 14 files with indirect coverage changes

(amount: string) => {
splitItem.onSplitExpenseAmountChange(splitItem.transactionID, Number(amount));
},
// eslint-disable-next-line react-compiler/react-compiler, react-hooks/exhaustive-deps

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.

Do we really need not to pass all dependencies?
If yes, could you please leave a comment on why we don't pass?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

The problem is that linter want to pass whole splitItem object to be passed as a dependency but the AI Reviewer dont like it and I think its a valid point that we shouldn't pass object as a dependency as it will recreate the callback each time some props of the object change even though it not have an impact on our callback, will leave a comment

@ZhenjaHorbach

ZhenjaHorbach commented Nov 6, 2025 •

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
    • MacOS: Desktop
  • 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 there are no new alerts related to the canBeMissing param for useOnyx
  • 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 shown in the product is localized by adding it to src/languages/* files and using the translation method
    • 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 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)
  • 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
  • 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.
  • 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.
  • 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
2026-01-27.10.04.26.mov
Android: mWeb Chrome
2026-01-27.10.04.26.mov
iOS: HybridApp
2026-01-27.09.51.28.mov
iOS: mWeb Safari
2026-01-27.09.55.16.mov
MacOS: Chrome / Safari
2026-01-27.09.37.13.mov
Details

@ZhenjaHorbach

Copy link
Copy Markdown
Contributor

I suppose we need to update Total amount info when we change amounts
Because now it doesn't take into account negative values

2025-11-06.16.26.23.mov

@ZhenjaHorbach

Copy link
Copy Markdown
Contributor

And I suppose we can change sign even when the original amount is not negative

2025-11-06.16.29.19.mov

@ZhenjaHorbach

Copy link
Copy Markdown
Contributor

When we split a transaction with a negative amount
and then try to edit the split items
The negative sign is missing from the amount

2025-11-06.16.31.21.mov

Also, on the edit split screen
The title does not show the negative sign

2025-11-06.16.32.31.mov

@kubabutkiewicz

Copy link
Copy Markdown
Contributor Author

hey @ZhenjaHorbach I will be checking this today

@kubabutkiewicz

Copy link
Copy Markdown
Contributor Author

@ZhenjaHorbach not sure about this issue

And I suppose we can change sign even when the original amount is not negative

whats wrong here I think this is correct behaviour now no?

@ZhenjaHorbach

ZhenjaHorbach commented Nov 7, 2025 •

Copy link
Copy Markdown
Contributor

@ZhenjaHorbach not sure about this issue

And I suppose we can change sign even when the original amount is not negative

whats wrong here I think this is correct behaviour now no?

Now we can use - sign only when the original transaction amount is negative
But in OD, we can change the sign even when the original transaction's amount is positive

@kubabutkiewicz

Copy link
Copy Markdown
Contributor Author

And that possible now also in ND, no ? Or I don't understand the issue 😅

Screen.Recording.2025-11-07.at.17.16.27.mov

@ZhenjaHorbach

ZhenjaHorbach commented Nov 7, 2025 •

Copy link
Copy Markdown
Contributor

And that possible now also in ND, no ?

Screen.Recording.2025-11-07.at.17.16.27.mov

Strange
Yesterday when I changed a sign, and when the input was out of focus
It reset the sign
But now everything seems to be working

@kubabutkiewicz

Copy link
Copy Markdown
Contributor Author

Hey @ZhenjaHorbach I think I fixed all the issues beside this

The title does not show the negative sign

As this is something I need to investigate as the transaction in onyx for this transaction have positive sign and needs to check if this is maybe a BE issue but will check next week.

Also we can treat it as a seprate issue and fix it in the follow up issue because its actually not related to original issue.

I will be off monday and tuesday and will be back to this on Wednesday.

@dubielzyk-expensify

Copy link
Copy Markdown
Contributor

Yeah I think that's a better idea, Shawn

@ZhenjaHorbach

Copy link
Copy Markdown
Contributor

@kubabutkiewicz
Could you please update the keyboard when you are free?

@kubabutkiewicz

Copy link
Copy Markdown
Contributor Author

@ZhenjaHorbach yes, working on this, checking why the changing of keyboardType is not working even I pass hardcoded different type to our input component 😅
image

@kubabutkiewicz

Copy link
Copy Markdown
Contributor Author

@ZhenjaHorbach Its done

@ZhenjaHorbach

Copy link
Copy Markdown
Contributor

LGTM!

@melvin-bot
melvin-bot Bot requested a review from lakchote February 3, 2026 18:08
@lakchote

lakchote commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

@kubabutkiewicz there are conflicts

@kubabutkiewicz

Copy link
Copy Markdown
Contributor Author

Will resolve soon

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

@lakchote
lakchote merged commit aa61f92 into Expensify:main Feb 4, 2026
29 checks passed
@github-actions

github-actions Bot commented Feb 4, 2026

Copy link
Copy Markdown
Contributor

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

@github-actions

github-actions Bot commented Feb 4, 2026

Copy link
Copy Markdown
Contributor

@OSBotify

OSBotify commented Feb 4, 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.

@OSBotify

OSBotify commented Feb 5, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/lakchote in version: 9.3.13-1 🚀

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

@OSBotify

OSBotify commented Feb 5, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/lakchote in version: 9.3.15-0 🚀

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/lakchote in version: 9.3.15-10 🚀

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

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.

9 participants