[CP Staging] Fix creating unexpected groups when creating a split from a group #32896

abzokhattab · 2023-12-12T04:13:00Z

Details

Fixed Issues

$ #32855
$ #32852
PROPOSAL: #32855 (comment)

Tests

Verify that no errors appear in the JS console

create a group chat with many members
open the chat and Click + > Split bill
Unselect a few members and create the bill split
validate that the request is created successfully and no new groups are created

Offline tests

create a group chat with many members
open the chat and Click + > Split bill
Unselect a few members and create the bill split
validate that the request is created successfully and no new groups are created

QA Steps

Verify that no errors appear in the JS console

create a group chat with many members
open the chat and Click + > Split bill
Unselect a few members and create the bill split
validate that the request is created successfully and no new groups are created

PR Author Checklist

Screenshots/Videos

Android: Native

Screen.Recording.2023-12-12.at.5.33.44.AM.mov

Android: mWeb Chrome

Screen.Recording.2023-12-12.at.5.39.11.AM.mov

iOS: Native

Screen.Recording.2023-12-12.at.5.33.44.AM.mov

iOS: mWeb Safari

Screen.Recording.2023-12-12.at.5.39.11.AM.mov

MacOS: Chrome / Safari

Screen.Recording.2023-12-12.at.5.41.49.AM.mov

MacOS: Desktop

Screen.Recording.2023-12-12.at.5.44.54.AM.mov

melvin-bot · 2023-12-12T04:13:06Z

@Santhosh-Sellavel 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]

situchan

Maybe update this code as well:

            if (iouType === CONST.IOU.TYPE.SPLIT) {
                IOU.splitBillAndOpenReport(
                    selectedParticipants,
                    currentUserPersonalDetails.login,
                    currentUserPersonalDetails.accountID,
                    transaction.amount,
                    trimmedComment,
                    transaction.currency,
                    transaction.category,
+                   transaction.tag,
+                   transaction.merchant,
                );

abzokhattab · 2023-12-12T04:33:16Z

Ok done

Julesssss

Simple fix, LGTM. I'll request a C+ review

shubham1206agra · 2023-12-12T11:33:45Z

I am here to review as per @Julesssss request

shubham1206agra · 2023-12-12T11:52:42Z

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 tests pass on all platforms & I tested again on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- 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 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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- 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 approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
- 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.js 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(themeColors.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 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.
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: Native

Screen.Recording.2023-12-12.at.5.05.04.PM.mov

Android: mWeb Chrome

iOS: Native

Screen.Recording.2023-12-12.at.5.35.47.PM.mov

iOS: mWeb Safari

Screen.Recording.2023-12-12.at.5.25.58.PM.mov

MacOS: Chrome / Safari

Screen.Recording.2023-12-12.at.5.21.35.PM.mov

MacOS: Desktop

Screen.Recording.2023-12-12.at.5.29.42.PM.mov

OSBotify · 2023-12-12T12:07:17Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

shubham1206agra · 2023-12-12T12:07:28Z

I was uploading videos one by one 😄

Julesssss · 2023-12-12T12:08:41Z

Ah, I saw what looked like all of them, I see now Android mWeb is missing, my bad.

shubham1206agra · 2023-12-12T12:12:12Z

No worries. It was all formality. I will upload the mWeb android later

…oups-when-creating-split-bill [CP Staging] Fix creating unexpected groups when creating a split from a group (cherry picked from commit 75041d0)

Julesssss · 2023-12-12T12:15:21Z

CP in progress

OSBotify · 2023-12-13T11:10:43Z

🚀 Deployed to production by https://github.com/Julesssss in version: 1.4.11-25 🚀

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

Fix Creating unexpected groups when creating a split from a group

6450cf9

abzokhattab requested a review from a team as a code owner December 12, 2023 04:13

melvin-bot bot requested review from Santhosh-Sellavel and removed request for a team December 12, 2023 04:13

situchan reviewed Dec 12, 2023

View reviewed changes

adding tag and merchant to split requests

732cd01

shubham1206agra mentioned this pull request Dec 12, 2023

[CP Staging] Track when a split is created from global create to call proper API #32878

Merged

47 tasks

Julesssss assigned abzokhattab Dec 12, 2023

Julesssss reviewed Dec 12, 2023

View reviewed changes

Julesssss mentioned this pull request Dec 12, 2023

Web - Split - Scan bill split is created in one of the participants' chat instead of new group chat #32895

Closed

4 tasks

mountiny changed the title ~~Fix creating unexpected groups when creating a split from a group~~ [CP Staging] Fix creating unexpected groups when creating a split from a group Dec 12, 2023

Julesssss approved these changes Dec 12, 2023

View reviewed changes

Julesssss merged commit 75041d0 into Expensify:main Dec 12, 2023
17 checks passed

github-actions bot mentioned this pull request Dec 12, 2023

Deploy Checklist: New Expensify 2023-12-11 #32794

Closed

81 tasks

Julesssss mentioned this pull request Dec 12, 2023

[HOLD for payment 2023-12-20] IOU - An error occurs when creating a Split Bill #32852

Closed

6 tasks

melvin-bot bot mentioned this pull request Dec 13, 2023

[HOLD for payment 2023-12-20] [$500] Split - A new group is formed when splitting bill with a few members in the group #32855

Closed

6 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[CP Staging] Fix creating unexpected groups when creating a split from a group #32896

[CP Staging] Fix creating unexpected groups when creating a split from a group #32896

abzokhattab commented Dec 12, 2023 •

edited by Julesssss

Loading

melvin-bot bot commented Dec 12, 2023

situchan left a comment

abzokhattab commented Dec 12, 2023

Julesssss left a comment

shubham1206agra commented Dec 12, 2023

shubham1206agra commented Dec 12, 2023 •

edited

Loading

OSBotify commented Dec 12, 2023

shubham1206agra commented Dec 12, 2023

Julesssss commented Dec 12, 2023

shubham1206agra commented Dec 12, 2023

Julesssss commented Dec 12, 2023

OSBotify commented Dec 13, 2023

[CP Staging] Fix creating unexpected groups when creating a split from a group #32896

[CP Staging] Fix creating unexpected groups when creating a split from a group #32896

Conversation

abzokhattab commented Dec 12, 2023 • edited by Julesssss Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Dec 12, 2023

situchan left a comment

Choose a reason for hiding this comment

abzokhattab commented Dec 12, 2023

Julesssss left a comment

Choose a reason for hiding this comment

shubham1206agra commented Dec 12, 2023

shubham1206agra commented Dec 12, 2023 • edited Loading

Reviewer Checklist

Screenshots/Videos

OSBotify commented Dec 12, 2023

shubham1206agra commented Dec 12, 2023

Julesssss commented Dec 12, 2023

shubham1206agra commented Dec 12, 2023

Julesssss commented Dec 12, 2023

OSBotify commented Dec 13, 2023

abzokhattab commented Dec 12, 2023 •

edited by Julesssss

Loading

shubham1206agra commented Dec 12, 2023 •

edited

Loading