Refactor createIOUTransaction to RequestMoney#10843
Conversation
|
Looks like you modified Instead, all new API commands should use API.js, and follow our guidelines for writing new API commands. Unsure if your change is okay? Drop a note in #expensify-open-source! |
|
Removing my review request as I'll be OOO all next week. Grab someone fresh with pullerbear when this is ready! |
There was a problem hiding this comment.
@Gonals Actually, I just noticed that the last message is not updated on the LHN when we are offline 😭
web.mov
1031f7a
|
@luacmartins, I could not reproduce the issue, but updating the lastMessage won't hurt and will get the optimistic report closer to the actual thing, so I did it anyways. It seems to test well! |
There was a problem hiding this comment.
LGTM and tests well (couldn't test offline on iOS simulator). Known issues:
- LHN last message is wiped when reconnecting. @Julesssss seems to be aware of this and working on a fix in #12082
- Unread message indicator is inconsistent. I think this has the same cause as https://github.com/Expensify/Expensify/issues/229696, since the ReconnectApp READ replaces the lastReadSequenceNumber before we send the WRITE request.
- I have verified the author checklist is complete (all boxes are checked off).
- I verified the correct issue is linked in the
### Fixed Issuessection 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
Testssection - I verified the steps for Staging and/or Production testing are in the
QA stepssection - 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.
toggleReportand 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 Copylabel 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 usingAvatarhave 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
thisproperly so there are no scoping issues (i.e. foronClick={this.submit}the methodthis.submitshould be bound tothisin the constructor) - Any internal methods bound to
thisare necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);ifthis.submitis 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
Avataris modified, I verified thatAvataris 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.
Web
web.mov
Desktop
desktop.mov
iOS
ios.mov
Safari
safari.mov
Android
android.mov
Chrome
chrome.mov
|
Gonna merge this since @mountiny and @Julesssss had approved it already. At this point, any issues that come up (aside from the known issues I mentioned above) should be minor and can be addressed as a polish follow up. Thanks for hanging on to this @Gonals! Awesome work! |
|
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
|
@Santhosh-Sellavel feel free to leave any post merge reviews. If you catch anything, we can open up issues to address any them. |
|
🚀 Deployed to staging by @luacmartins in version: 1.2.20-0 🚀
|
|
Great work @Gonals, I think you should take the rest of the day off to celebrate |
|
🚀 Deployed to production by @chiragsalian in version: 1.2.20-3 🚀
|
|
Sorry for the delay, since this is merged, focused on other issues. Since this is deployed. Tested on staging but fails, and ran into something went wrong. Steps:
A Red dot appeared on those chats. Shows an error, refer video for more. Desktop.mov |
Santhosh-Sellavel
left a comment
There was a problem hiding this comment.
Code Looks good, I feel unit tests are missed for independent Utils.
| function calculateAmount(participants, total, isDefaultUser = false) { | ||
| // Convert to cents before working with iouAmount to avoid | ||
| // javascript subtraction with decimal problem -- when dealing with decimals, | ||
| // because they are encoded as IEEE 754 floating point numbers, some of the decimal | ||
| // numbers cannot be represented with perfect accuracy. | ||
| // Cents is temporary and there must be support for other currencies in the future | ||
| const iouAmount = Math.round(parseFloat(total * 100)); | ||
| const totalParticipants = participants.length + 1; | ||
| const amountPerPerson = Math.round(iouAmount / totalParticipants); | ||
|
|
||
| if (!isDefaultUser) { | ||
| return amountPerPerson; | ||
| } | ||
|
|
||
| const sumAmount = amountPerPerson * totalParticipants; | ||
| const difference = iouAmount - sumAmount; | ||
|
|
||
| return iouAmount !== sumAmount ? (amountPerPerson + difference) : amountPerPerson; | ||
| } |
There was a problem hiding this comment.
Can we add unit tests for this file?
There was a problem hiding this comment.
Those are quite good shouts, I think such issues could be external, what do you think @Julesssss @luacmartins @Gonals
| function buildOptimisticIOUReportAction(sequenceNumber, type, amount, currency, comment, paymentType = '', iouTransactionID = '', iouReportID = '', debtorEmail = '', locale = 'en') { | ||
| const IOUTransactionID = iouTransactionID || NumberUtils.rand64(); |
There was a problem hiding this comment.
Not sure why unit tests for this missed out.
what about this one |
|
@Santhosh-Sellavel Can you report this in the Slack channel, that might be the best way forward. Thanks! |
|
Hey! @Gonals (that's me!) @mountiny @Julesssss @luacmartins, this introduced a bug here: #13511 |
|
👋 Hey y'all! Some of you are aware since I tagged you when initially working on the bug, but for everyone's benefit and to complete the Bug Zero checklist: this PR resulted in a bug here #12432 |
Details
Fixed Issues
$ https://github.com/Expensify/Expensify/issues/211961
Tests
Let's do this!
+button and choose someone with NO chat with you.PR Review Checklist
PR Author Checklist
### Fixed Issuessection aboveTestssectionQA stepssectiontoggleReportand notonIconClick)src/languages/*filesWaiting for Copylabel for a copy review on the original GH to get the correct copy.STYLE.md) were followedAvatar, I verified the components usingAvatarare working as expected)/** comment above it */thisproperly so there are no scoping issues (i.e. foronClick={this.submit}the methodthis.submitshould be bound tothisin the constructor)thisare necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);ifthis.submitis never passed to a component event handler likeonClick)StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)Avataris modified, I verified thatAvataris 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 Issuessection aboveTestssectionQA stepssectiontoggleReportand notonIconClick).src/languages/*filesWaiting for Copylabel for a copy review on the original GH to get the correct copy.STYLE.md) were followedAvatar, I verified the components usingAvatarhave been tested & I retested again)/** comment above it */thisproperly so there are no scoping issues (i.e. foronClick={this.submit}the methodthis.submitshould be bound tothisin the constructor)thisare necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);ifthis.submitis never passed to a component event handler likeonClick)StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)Avataris modified, I verified thatAvataris 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 Issuessection aboveTestssectionQA stepssectiontoggleReportand notonIconClick).src/languages/*filesSTYLE.md) were followedAvatar, I verified the components usingAvatarhave been tested & I retested again)/** comment above it */thisproperly so there are no scoping issues (i.e. foronClick={this.submit}the methodthis.submitshould be bound tothisin the constructor)thisare necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);ifthis.submitis never passed to a component event handler likeonClick)StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)Avataris modified, I verified thatAvataris working as expected in all cases)QA Steps
Same as tests