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

Feature/35716 changing owner flow #37869

Merged
merged 73 commits into from
Mar 26, 2024

Conversation

burczu
Copy link
Contributor

@burczu burczu commented Mar 7, 2024

Details

This PR introduces ability to change ownership of the paid workspace as part of the Simplified collect project.

Fixed Issues

$ #35716
PROPOSAL: n/a

Tests

  1. Log in to the App as an admin of the paid workspace who is not an owner at the same time
  2. Open paid workspace
  3. Go to Members page
  4. Click on the owner of the workspace
  5. Click "Transfer owner"
  6. Follow instructions and check if everything works correctly
  • Verify that no errors appear in the JS console

Offline tests

Changing ownership is not available in offline mode - check if the "Transfer owner" button is disabled

QA Steps

  • Verify that no errors appear in the JS console

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 the expected offline behavior in the Offline steps 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 tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
    • 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 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
      • If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • 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 either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • 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
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • 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(theme.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 the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • 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.

Screenshots/Videos

Android: Native
Screen.Recording.2024-03-25.at.13.01.29.mov
Android: mWeb Chrome
Screen.Recording.2024-03-25.at.12.53.37.mov
iOS: Native
Screen.Recording.2024-03-25.at.12.45.51.mov
iOS: mWeb Safari
Screen.Recording.2024-03-25.at.12.48.50.mov
MacOS: Chrome / Safari
Screen.Recording.2024-03-25.at.12.18.04.mov
MacOS: Desktop
Screen.Recording.2024-03-25.at.12.21.19.mov

@burczu burczu force-pushed the feature/35716-changing-owner-flow branch from 2660d0c to 2124c90 Compare March 7, 2024 09:29
@burczu burczu force-pushed the feature/35716-changing-owner-flow branch from e14442c to 2d361a8 Compare March 8, 2024 06:28
Copy link
Contributor

@luacmartins luacmartins left a comment

Choose a reason for hiding this comment

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

Looking better. I left a couple of comments. In addition, we have the following issues:

  1. Unknown error page is not shown. I couldn't get to the unknown error page even when I got a 405 Resource in incorrect state error
error.mov
  1. Stale error shows momentarily when navigating and before loading spinner
staleDataShows.mov

src/libs/WorkspacesSettingsUtils.ts Outdated Show resolved Hide resolved
src/ROUTES.ts Outdated Show resolved Hide resolved
@luacmartins
Copy link
Contributor

It seems like the TS error might be related to cache. I see that we disable the default export error here.

Error: workflow_tests/failureNotifier.test.ts(6,8): error TS1192: Module '"/home/runner/work/App/App/workflow_tests/mocks/failureNotifierMocks"' has no default export.

@burczu
Copy link
Contributor Author

burczu commented Mar 26, 2024

@luacmartins I've just addressed your last comments including a refactor to handle payment card form inside the common change owner check page. Regarding bugs, you've raised:

  1. Unknown error page is not shown. I couldn't get to the unknown error page even when I got a 405 Resource in incorrect state error

This was because I had to work with mocked API, and my assumption was that I'll get an errorFields object with some unexpected error messages - based on the example you've shown in your comment, it looks like in this case the errorFields object is cleared, so I've change the implementation accordingly and it should (hopefully) work now as expected. Please test it one more time.

  1. Stale error shows momentarily when navigating and before loading spinner

I think I've managed to fix this for the case when we open the modal for the first time (like you've shown in the screen capture video). But there is still a glitch when we switch between errors in the opened modal - in some cases after the loader disappears, we see the previous texts for milliseconds. I didn't find out yet how to fix it, and will continue working on this, but maybe we could try to address it in a follow up issue in the worst case scenario?

@burczu
Copy link
Contributor Author

burczu commented Mar 26, 2024

@shawnborton regarding your comments:

The "Woohoo" area doesn't quite feel vertically centered in the space below the top page header area and the bottom green button. Can you check that out?

It is vertically centered:

Screenshot 2024-03-26 at 11 02 22

The feeling that there is something wrong with the alignment comes from the fact that there is a lot of empty space in the animation/image. I've used existing component for this that we use, e.g., in the enable payment process or in the wallet's transfer balance page.

For these screens:
CleanShot 2024-03-25 at 10 14 08@2x

Can we tighten up the gap between headline and text? Maybe try 8px gap below the headline?

Do you mean the gap between the "Transfer owner" and "Outstanding balance" or between "Outstanding balance" and "The account owning the workspace..." text?

@shawnborton
Copy link
Contributor

The feeling that there is something wrong with the alignment comes from the fact that there is a lot of empty space in the animation/image. I've used existing component for this that we use, e.g., in the enable payment process or in the wallet's transfer balance page.

Sounds good, thanks for confirming.

or between "Outstanding balance" and "The account owning the workspace..." text?

This, the headline and the text immediately below it.

@burczu
Copy link
Contributor Author

burczu commented Mar 26, 2024

@shawnborton Thanks for the answer. I've just changed the gap to 8px, as requested - it will look like below:

Screenshot 2024-03-26 at 14 34 35
Screenshot 2024-03-26 at 14 36 53

@shawnborton
Copy link
Contributor

Thanks for the answer. I've just changed the gap to 8px, as requested - it will look like below:

Looks good, thanks!

Copy link
Contributor

@luacmartins luacmartins left a comment

Choose a reason for hiding this comment

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

Code LGTM. I'm still seeing a few small things that we need to address, but those can be done in a follow up:

  1. Disable Transfer owner button if user is offline since we can only go through this flow while online.

  2. Wrong error flashes momentarily

error_flash.mov
  1. We're showing an error screen on success after adding a debit card
error_page_on_success.mov
  1. We're showing three decimals for USD currency

three_decimals

@luacmartins
Copy link
Contributor

I'll do the checklist on this one since it's hard for C+ to test it because we need the API in certain states to trigger errors.

@luacmartins
Copy link
Contributor

luacmartins commented Mar 26, 2024

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 either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • 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(theme.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 the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • 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
android.mov
Android: mWeb Chrome
chrome.mov
iOS: Native
ios.mov
iOS: mWeb Safari
safari.mov
MacOS: Chrome / Safari
web.mov
MacOS: Desktop
desktop.mov

@luacmartins luacmartins merged commit 0702d16 into Expensify:main Mar 26, 2024
15 checks passed
@OSBotify
Copy link
Contributor

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

Comment on lines +2165 to +2167
failedToClearBalanceTitle: 'Failed to clear balance',
failedToClearBalanceButtonText: 'OK',
failedToClearBalanceText: 'We were unable to clear the balance. Please try again later.',
Copy link
Contributor

@iwiznia iwiznia May 8, 2024

Choose a reason for hiding this comment

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

How come this is in english? This is against the checklists @burczu @luacmartins

Please send a PR to fix this @burczu

Copy link
Contributor

Choose a reason for hiding this comment

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

Damn, I thought we had updated all of them, but clearly we missed some. I'll put up a PR to fix it. Thanks for raising this.

onClose={() => onClose?.()}
onModalHide={onClose}
hideModalContentWhileAnimating
useNativeDriver
Copy link
Contributor

Choose a reason for hiding this comment

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

We forgot to add onBackdropPress here which is causing inconsistency in the flow. More details #47559

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.