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

Added shouldShowOfflineIndicator default props #20467

Merged
merged 17 commits into from
Jun 20, 2023

Conversation

dhairyasenjaliya
Copy link
Contributor

@dhairyasenjaliya dhairyasenjaliya commented Jun 8, 2023

Details

Fixed Issues

$ #20004
PROPOSAL: #20004 (comment)

Tests

  1. Switch to offline
  2. Create new workspace(if not created)
  3. Go to any workspace > bank account
  4. Select Connect online with Plaid option
  5. Notice on native mobile / mWeb should show only one OfflineIndicator

Test 2 (Add personal bank account)

  1. Log in to the account without the beta wallet
  2. Go to Settings > Preferences > enable Use Staging Server
  3. Add a new bank account:
    • Wells Fargo
    • Username: user_good
    • password: pass_good
    • Mobile verification code: credential_good
  4. Turn off the internet notice you should get You appears to be offline since here we can’t perform any step on offline mode

Test 3 (Bank account plaid step)

  1. Login to ND (Switch to offline)
  2. Go to Settings > Go to any workspace
  3. Go to bank account
  4. Notice on native mobile / mWeb should show only one OfflineIndicator

Test 4 (Code page )

  1. Login to ND (Switch to offline)
  2. Go to Settings > Go to security
  3. Go to Two-factor authentication
  4. Notice on native mobile / mWeb should show only one OfflineIndicator

Test 5 (Verify page )

  1. Login to ND (Switch to offline)
  2. Go to Settings > Go to security
  3. Go to Two-factor authentication
  4. Perform step-1 by clicking/downloading code -> Press Next
  5. Notice on native mobile / mWeb should show only one OfflineIndicator

Test 6 (Success page )

  1. Login to ND Go to Settings > Go to security
  2. Go to Two-factor authentication
  3. Perform step-1 by clicking/downloading code -> Press Next
  4. Add auth code -> Press next -> On success page -> (Switch to offline)
  5. Notice on native mobile / mWeb should show only one OfflineIndicator

Test 7 (bank account)

  1. Login to ND with phone number
  2. Go to setting -> Go to any workspace
  3. Go to bank account
  4. Notice you appears to be offline should show at bottom same as other page
  • Verify that no errors appear in the JS console

Offline tests

Same as above

QA Steps

  • Same as above 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 / Chrome
    • iOS / native
    • iOS / 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 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
  • 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 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(themeColors.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 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 author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web webChrome
Mobile Web - Chrome mobileChrome
Mobile Web - Safari
Desktop Desktop
iOS
Android
Test 2-6 https://github-production-user-asset-6210df.s3.amazonaws.com/47522946/246508396-e808af18-1858-49cd-8307-d921fbf4fab5.png

@dhairyasenjaliya dhairyasenjaliya marked this pull request as ready for review June 8, 2023 18:51
@dhairyasenjaliya dhairyasenjaliya requested a review from a team as a code owner June 8, 2023 18:51
@melvin-bot melvin-bot bot requested review from flodnv and thesahindia and removed request for a team June 8, 2023 18:51
@melvin-bot
Copy link

melvin-bot bot commented Jun 8, 2023

@flodnv @thesahindia 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]

@@ -88,6 +88,7 @@ class AddPersonalBankAccountPage extends React.Component {
<ScreenWrapper
includeSafeAreaPaddingBottom={shouldShowSuccess}
shouldEnablePickerAvoiding={false}
shouldShowOfflineIndicator={false}
Copy link
Member

Choose a reason for hiding this comment

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

Looks like we will need the offline indicator here

Screen.Recording.2023-06-09.at.10.00.34.PM.mov

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@thesahindia Even if I remove the props still there is no offline indicator, this bug exists on the main as well un-related to PR
Screenshot 2023-06-09 at 10 54 33 PM

Copy link
Contributor Author

@dhairyasenjaliya dhairyasenjaliya Jun 9, 2023

Choose a reason for hiding this comment

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

@thesahindia I agree we should add <FullPageOfflineBlockingView> to plaid and I found that initially this might be missed to add <FullPageOfflineBlockingView> here AddPlaidBankAccount.js but I believe this should be treated as a separate bug and treated into another PR since this PR is just about to remove the duplicate indicator
let me know if this sounds fine

Changes to add OfflineBlockingView to AddPlaidBankAccount when we have account's

+ <FullPageOfflineBlockingView>

Copy link
Member

Choose a reason for hiding this comment

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

I am not sure about it. I think we should handle it here. It's a simple change.

Copy link
Member

Choose a reason for hiding this comment

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

cc: @flodnv for thoughts.

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes please let's just make this change here @dhairyasenjaliya

Copy link
Member

Choose a reason for hiding this comment

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

Please always add a new comment instead of editing an existing comment, as it can often go unnoticed.

@dhairyasenjaliya, can you please add some more details? I am not sure I understand how this is related to FullPageOfflineBlockingView.

@dhairyasenjaliya
Copy link
Contributor Author

@thesahindia I have added FullPageOfflineBlockingView to AddPlaidBankAccount

@thesahindia
Copy link
Member

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 / Chrome
    • iOS / native
    • iOS / 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 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
  • 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(themeColors.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 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

Web Screenshot 2023-06-16 at 2 36 52 AM Screenshot 2023-06-16 at 2 35 18 AM
Mobile Web - Chrome Screenshot 2023-06-16 at 2 43 25 AM
Mobile Web - Safari Screenshot 2023-06-16 at 2 56 19 AM
Desktop Screenshot 2023-06-16 at 2 37 53 AM Screenshot 2023-06-16 at 2 38 00 AM
iOS Screenshot 2023-06-16 at 2 52 56 AM
Android Screenshot 2023-06-16 at 2 50 01 AM

Copy link
Member

@thesahindia thesahindia left a comment

Choose a reason for hiding this comment

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

Looks good!

cc: @flodnv

Copy link
Contributor

@flodnv flodnv left a comment

Choose a reason for hiding this comment

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

Thanks! @dhairyasenjaliya Can you please update your tests and screenshots to test all the pages you have modified in this PR? 🙏

@dhairyasenjaliya
Copy link
Contributor Author

@flodnv @thesahindia the position of the message is expected or not since the rest all have at the bottom this one is not ?

@flodnv
Copy link
Contributor

flodnv commented Jun 16, 2023

I am not sure, maybe not? Maybe ask in Slack? What is causing this different behavior? 😕

@dhairyasenjaliya
Copy link
Contributor Author

dhairyasenjaliya commented Jun 16, 2023

@flodnv we have just missed to add <Scrollview> and i checked this was 2 year back code when we logged in using phone number and try to add account we show warning at that time offline indicatore has different position & this is minor change

Screenshot 2023-06-16 at 11 23 54 PM

@flodnv
Copy link
Contributor

flodnv commented Jun 16, 2023

Oh, if it's easy to fix it then let's also fix it here please

@dhairyasenjaliya
Copy link
Contributor Author

yeah just came in while testing all the steps again :)

@dhairyasenjaliya
Copy link
Contributor Author

@flodnv @thesahindia
7 additional steps were added with a screenshot of mobile since this PR affects only mobile and also additional fixes of offline indicator added (test 7) ready to merge :)

Copy link
Member

@thesahindia thesahindia left a comment

Choose a reason for hiding this comment

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

The changes looks good to me!

cc: @flodnv

@melvin-bot melvin-bot bot requested a review from flodnv June 19, 2023 09:40
@flodnv
Copy link
Contributor

flodnv commented Jun 19, 2023

You have conflicts 😬

@dhairyasenjaliya
Copy link
Contributor Author

looks like position of indicator is being fixed somewhere else but conflict solved @flodnv

@flodnv
Copy link
Contributor

flodnv commented Jun 19, 2023

Your last commit is still not verified 😬

@dhairyasenjaliya
Copy link
Contributor Author

yeah something is off im looking into

@dhairyasenjaliya dhairyasenjaliya force-pushed the offlineIndicator branch 3 times, most recently from b995581 to ef63157 Compare June 19, 2023 21:05
@dhairyasenjaliya
Copy link
Contributor Author

@flodnv conflict resolved ready to merge pr:)

@flodnv flodnv merged commit 6d53998 into Expensify:main Jun 20, 2023
@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.

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/flodnv in version: 1.3.30-0 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/luacmartins in version: 1.3.30-5 🚀

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

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.

5 participants