Skip to content
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

[Refactor] Use CloseAccount to replace User_Delete and refactor related pages #9635

Merged
merged 31 commits into from
Aug 1, 2022

Conversation

Beamanator
Copy link
Contributor

@Beamanator Beamanator commented Jun 30, 2022

cc @Julesssss since you worked on the Close Account project

Holding on related Web-E PR: https://github.com/Expensify/Web-Expensify/pull/34159

Details

See fixed issue for design doc ref

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/213701

Tests (both Dev & Staging)

Same as mentioned in https://github.com/Expensify/Web-Expensify/pull/34159

  • Verify that no errors appear in the JS console

PR Review Checklist

Contributor (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 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 included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • iOS / native
    • Android / native
    • iOS / Safari
    • Android / Chrome
    • MacOS / Chrome
    • 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 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 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 tagging the marketing team 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 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.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 */
    • Any functional components have the displayName property
    • 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
  • 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 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.

Screenshots

Web & Desktop

VidCloseAccount.mov

Mobile Web

iOS

Android

@Beamanator Beamanator self-assigned this Jun 30, 2022
@melvin-bot
Copy link

melvin-bot bot commented Jun 30, 2022

Looks like you modified deprecatedAPI.js! To be clear, you should not be adding any code to this file.

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!

@Beamanator
Copy link
Contributor Author

One problem to solve before marking ready for review: https://expensify.slack.com/archives/C02HWMSMZEC/p1656604993085699

@Beamanator Beamanator marked this pull request as ready for review July 1, 2022 15:39
@Beamanator Beamanator requested a review from a team as a code owner July 1, 2022 15:39
@Beamanator Beamanator requested review from a team and removed request for a team July 1, 2022 15:39
@melvin-bot melvin-bot bot requested review from youssef-lr and removed request for a team July 1, 2022 15:39
Copy link
Contributor

@marcaaron marcaaron left a comment

Choose a reason for hiding this comment

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

This LGTM

src/ONYXKEYS.js Outdated Show resolved Hide resolved
@Beamanator
Copy link
Contributor Author

Thanks for the reviews so far gents! Comments addressed 👍

@Beamanator
Copy link
Contributor Author

Needs an Onyx version bump before it will test well 👍

@Beamanator
Copy link
Contributor Author

Please feel free to review with your morning coffee :)

marcaaron
marcaaron previously approved these changes Jul 19, 2022
@marcaaron
Copy link
Contributor

Looks great, thanks for the changes and discussion 🙇

Comment on lines 23947 to 23948
"integrity": "sha1-BqZgTWpV1L9BqaR9mHLXp42jHnM="
"integrity": "sha512-xpkr6sCDIYTPqzvjG8M3ncw1YOTaloWZOyrUmicoEifBEKzQzt+ooUpRpQ/AbOoJfO/p2ZKiyp79qHThzJDulQ=="
},
Copy link
Contributor

Choose a reason for hiding this comment

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

@Beamanator are you on an older MBP? I think we agreed to stop commiting these changes unless you have an M1 MMP

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh interesting! I must have missed that - I'm on an Intel still, my M1 will be arriving during offshore 😅

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'll remove these unnecessary edits, thanks for calling this out

Julesssss
Julesssss previously approved these changes Jul 19, 2022
Copy link
Contributor

@Julesssss Julesssss left a comment

Choose a reason for hiding this comment

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

Left one question, but looking good

@Beamanator Beamanator dismissed stale reviews from Julesssss and marcaaron via 200e5a8 July 19, 2022 09:51
@Beamanator
Copy link
Contributor Author

Updated @Julesssss 👍

Julesssss
Julesssss previously approved these changes Jul 19, 2022
@Beamanator Beamanator mentioned this pull request Jul 21, 2022
88 tasks
@Beamanator
Copy link
Contributor Author

wtf I didn't notice this didn't get merged 🙃 I'll fix conflicts today

@Beamanator
Copy link
Contributor Author

Conflicts fixed, got 2 previous approvals so if anyone wants to approve again we can merge

@Julesssss
Copy link
Contributor

Still testing well:

Prevented from closing
Screenshot 2022-08-01 at 14 52 52

Closed and data is cleared
Screenshot 2022-08-01 at 14 56 28

@Julesssss Julesssss merged commit 4a9fa9b into main Aug 1, 2022
@Julesssss Julesssss deleted the beaman-refactorUserDelete branch August 1, 2022 13:57
@OSBotify
Copy link
Contributor

OSBotify commented Aug 1, 2022

✋ 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
Copy link
Contributor

OSBotify commented Aug 1, 2022

🚀 Deployed to staging by @Julesssss in version: 1.1.87-0 🚀

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

@OSBotify
Copy link
Contributor

OSBotify commented Aug 4, 2022

🚀 Deployed to production by @yuwenmemon in version: 1.1.87-9 🚀

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

initWithStoredValues: false,
closeAccount: {
key: ONYXKEYS.CLOSE_ACCOUNT,
initWithStoredValues: {error: '', isLoading: false},
Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ohhhhh interesting, good catch. It looks like in that repo we default initWithStoredValues to true so I think I can pretty much just delete this line - we do actually want to load the page with the error / loading state stored

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.

4 participants