Remove Report_IOUs key from Onyx#12780
Conversation
|
@mollfpr @aldo-expensify 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] |
|
There is one new console error, but it will get fixed after the cleanup |
|
Ready for review! Only HELD by the Web-E counterpart |
ScreenshotsWebMobile Web - ChromeMobile Web - SafariDesktop12780.Desktop.moviOS12780.iOS.movAndroid12780.Android.mov |
|
The Screen.Recording.2022-11-18.at.20.11.38.movScreen.Recording.2022-11-18.at.20.17.52.mov |
mountiny
left a comment
There was a problem hiding this comment.
The code looks good to me. The web api code is in staging so @mollfpr you can now test if you build the apps with staging API. So you need to build desktop app for web and in native apps probably hardcode the staging url
We need to wait for the PR to be in production before merging though
|
@Gonals There are some merge conflicts, can you please resolve them? |
|
Conflicts solved! |
mountiny
left a comment
There was a problem hiding this comment.
Tested well, putting this back on hold for the PR since we cannot merge this before we hit production on the web API PR.
I have included videos in this comment with the checklist #12780 (comment)
Wont merge yet
There was a problem hiding this comment.
LGTM 👍
The checklist and videos #12780 (comment)
|
@Gonals Once again merge conflicts 🙇 |
Solved! |
|
https://github.com/Expensify/Web-Expensify/pull/35594 was deployed to production ~3 hours ago, should we remove the hold or wait a bit? |
|
I think we can remove yeah |
|
OFF HOLD, then! Let's do this 🎉 |
|
Yup, I guess I can test with DEV env now? |
You should be able to test normally now, yep :) |
|
Awesome! I think we are good to merge, then, @mountiny @aldo-expensify |
|
@aldo-expensify feel free to merge once you get online. thanks @mollfpr for testing 🙇 |
|
✋ 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 @aldo-expensify in version: 1.2.34-0 🚀
|
|
🚀 Deployed to production by @luacmartins in version: 1.2.34-1 🚀
|

Details
Fixed Issues
$ #10525
Tests
This doesn't add new functionality, so we should just do general flow tests to confirm nothing broke:
Offline tests
There should be no relevant offline behavior changes
QA Steps
Same as tests
PR Author Checklist
I linked the correct issue in the
### Fixed Issuessection aboveI wrote clear testing steps that cover the changes made in this PR
TestssectionOffline stepssectionQA stepssectionI included screenshots or videos for tests on all platforms
I ran the tests on all platforms & verified they passed on:
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 followed proper code patterns (see Reviewing the code)
toggleReportand notonIconClick)src/languages/*filesWaiting for Copylabel for a copy review on the original GH to get the correct copy.STYLE.md) were followedIf 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 usingAvatarare 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.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:
/** 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)If a new CSS style is added I verified that:
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 author checklist, including those that don't apply to this PR.
PR Reviewer Checklist
The reviewer will copy/paste it into a new comment and complete it after the author checklist is completed
### Fixed Issuessection aboveTestssectionOffline stepssectionQA 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)Screenshots
No real UI changes