-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only update IOU total when network is online and the request currency matches the IOUReport's #12488
Conversation
The second point of expected result in #12433 says that the pay IOU should be disabled. @youssef-lr Is that gonna be done in a seperate PR? |
@rushatgabhane I will implement it in this PR. |
sweet! |
Reviewer Checklist
Screenshots/VideosWeb2022-11-07_10-30-34.mp4Mobile Web - ChromeMobile Web - SafariDesktopiOSAndroid |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested well and code LGTM!
@@ -65,6 +65,7 @@ function requestMoney(report, amount, currency, recipientEmail, participant, com | |||
iouReports[`${ONYXKEYS.COLLECTION.REPORT_IOUS}${chatReport.iouReportID}`], | |||
recipientEmail, | |||
amount, | |||
currency, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are more usages of IOUUtils.updateIOUOwnerAndTotal
. We'll need to update those too, e.g.
Lines 340 to 344 in 2820c72
oneOnOneIOUReport = IOUUtils.updateIOUOwnerAndTotal( | |
existingIOUReport, | |
currentUserEmail, | |
splitAmount, | |
); |
Line 572 in 2820c72
const updatedIOUReport = IOUUtils.updateIOUOwnerAndTotal(iouReport, currentUserEmail, amount, type); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is in createSplitsAndOnyxData
, do you think it should have the same behavior?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we still add the money request to the individual IOU report with each user.
@youssef-lr please ping me whenever you've pushed changes to disable the pay button. Thanks! 🙇♂️ |
@rushatgabhane disabling the Pay button will be implemented in an upcoming refactor I'm working on, so it won't be included in this PR. |
Updated! Working on screen recordings and updating test steps. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I won't be able to test this since I'm going ooo today until Nov 22, but changes LGTM! Thanks for fixing this!
code looks good, testing after the shiny new test steps arrive ✨ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
@youssef-lr please ping me when you've updated the tests, thanks! |
@rushatgabhane updated! Sorry for the delay I had some issues in my dev environment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@youssef-lr thank you, we're good to merge :)
Web
Screen.Recording.2022-11-15.at.9.10.50.PM.mov
Screen.Recording.2022-11-15.at.9.15.45.PM.mov
mWeb
Screen.Recording.2022-11-15.at.9.18.40.PM.mov
Screen.Recording.2022-11-15.at.9.25.53.PM.mov
iOS
Screen.Recording.2022-11-15.at.9.39.49.PM.mov
Android
WhatsApp.Video.2022-11-15.at.22.40.52.mp4
Desktop
Screen.Recording.2022-11-15.at.9.45.18.PM.mov
PR 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 verified the steps for local testing are in the
- 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:
- iOS / native
- Android / native
- iOS / Safari
- Android / Chrome
- MacOS / Chrome
- 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 notonIconClick
). - 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 was added in all
src/languages/*
files - I verified any copy / text that was added to the app is correct English and 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
- 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.
- 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 usingAvatar
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. foronClick={this.submit}
the methodthis.submit
should be bound tothis
in the constructor) - Any internal methods bound to
this
are necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);
ifthis.submit
is never passed to a component event handler likeonClick
) - 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 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 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 thatAvatar
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.
- I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.
Thanks @rushatgabhane! |
@youssef-lr looks like this was merged without the checklist test passing. Please add a note explaining why this was done and remove the |
PR Author checklist is complete Melvin. |
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
🚀 Deployed to staging by @youssef-lr in version: 1.2.28-0 🚀
|
🚀 Deployed to staging by @youssef-lr in version: 1.2.28-0 🚀
|
🚀 Deployed to production by @roryabraham in version: 1.2.28-2 🚀
|
* @param {String} type | ||
* @returns {Object} | ||
*/ | ||
function updateIOUOwnerAndTotal(iouReport, actorEmail, amount, type = CONST.IOU.REPORT_ACTION_TYPE.CREATE) { | ||
function updateIOUOwnerAndTotal(iouReport, actorEmail, amount, currency, type = CONST.IOU.REPORT_ACTION_TYPE.CREATE) { | ||
if (currency !== iouReport.currency && isNetworkOffline) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this should be only if the user is offline. If I request money in different currency even when being online, I will create optimistic report which will change the total locally to wrong number before this will be fetched from the server to the correct amount.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mountiny that makes sense to me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah i think this could end up with the flickering issues.
cc @youssef-lr maybe something we should address in the related issues
heads-up: I think from this PR we have noticed an issue which we havent spotted here #12792 where the IOU preview was flashing if we cancelled a request with different currency. |
Details
This PR prevents any updates to be made to the IOU total when the user requests money while offline and the IOU request currency is different from the IOU report currency. Once connection is restored the IOU gets updated correctly.
Fixed Issues
$ #12433
Tests
QA Steps
Test requesting money
Test cancelling money request
PR Author Checklist
### Fixed Issues
section aboveTests
sectionQA steps
sectiontoggleReport
and notonIconClick
)src/languages/*
filesSTYLE.md
) were followedAvatar
, I verified the components usingAvatar
are working as expected)/** comment above it */
this
properly so there are no scoping issues (i.e. foronClick={this.submit}
the methodthis.submit
should be bound tothis
in the constructor)this
are necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);
ifthis.submit
is never passed to a component event handler likeonClick
)StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG
)Avatar
is modified, I verified thatAvatar
is working as expected in all cases)PR Reviewer Checklist
The reviewer will copy/paste it into a new comment and complete it after the author checklist is completed
### Fixed Issues
section aboveTests
sectionQA steps
sectiontoggleReport
and notonIconClick
).src/languages/*
filesWaiting for Copy
label for a copy review on the original GH to get the correct copy.STYLE.md
) were followedAvatar
, I verified the components usingAvatar
have been tested & I retested again)/** comment above it */
this
properly so there are no scoping issues (i.e. foronClick={this.submit}
the methodthis.submit
should be bound tothis
in the constructor)this
are necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);
ifthis.submit
is never passed to a component event handler likeonClick
)StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG
)Avatar
is modified, I verified thatAvatar
is working as expected in all cases)Screenshots
Web
offline_iou_web.mov
Mobile Web - Chrome
sr.-.android.-.chrome.mov
Mobile Web - Safari
RPReplay_Final1668386838.mov
Desktop
sr.desktop.mov
iOS
RPReplay_Final1668361307.MP4
Android
sr.-.android.-.native.mov