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

Make Compose box accessible before the chat loads #16705

Conversation

getusha
Copy link
Contributor

@getusha getusha commented Mar 29, 2023

Details

Fixed Issues

$ #14223
PROPOSAL: #14223 (comment)

Tests

Same as QA steps

  • Verify that no errors appear in the JS console

Offline tests

  1. Open any old chat or a chat that is still loading.
  2. Type a message in the compose box.
  3. Open EmojiPicker and insert an emoji
  4. Send the message by clicking the send icon
  5. Add any attachment and send, go to the compose box and click on the left "+" icon.
  6. Confirm Sending, splitting, requesting money works as expected
  7. Verify that the compose box is accessible and functioning properly as it would when the device is connected to the internet

QA Steps

  1. Disconnect the device from the internet.
  2. Open any old chat or a chat that is still loading.
  3. Type a message in the compose box.
  4. Open EmojiPicker and insert an emoji
  5. Send the message by clicking the send icon
  6. Add any attachment and send, go to the compose box and click on the left "+" icon.
  7. Confirm Sending, splitting, requesting money works as expected
  8. Verify that the compose box is accessible and functioning properly as it would when the device is connected to the internet
  • 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 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 correct English and 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 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
Screen.Recording.2023-03-31.at.7.12.24.AM.mov
Mobile Web - Chrome
Screen.Recording.2023-03-31.at.7.19.03.AM.mov
Mobile Web - Safari
Screen.Recording.2023-03-31.at.7.25.49.AM.mov
Desktop
Screen.Recording.2023-03-31.at.8.21.33.AM.mov
iOS
Screen-Recording-2023-03-31-at-9.1.mp4
Android
Screen-Recording-2023-03-31-at-8.1.mp4

@getusha getusha requested a review from a team as a code owner March 29, 2023 19:42
@melvin-bot melvin-bot bot requested review from sobitneupane and techievivek and removed request for a team March 29, 2023 19:42
@MelvinBot
Copy link

@techievivek @sobitneupane 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]

@sobitneupane
Copy link
Contributor

@getusha Can you please add testing steps to cover other scenarios like adding emoji, performing IOU operations, sending attachments, etc while the report is still loading.

@getusha
Copy link
Contributor Author

getusha commented Mar 30, 2023

@sobitneupane updated, let me know if i need to add more.

Copy link
Contributor

@sobitneupane sobitneupane left a comment

Choose a reason for hiding this comment

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

Screenshots/Videos

Web
test.mov
Mobile Web - Chrome
Screen.Recording.2023-03-30.at.16.16.56.mov
Mobile Web - Safari
Screen.Recording.2023-03-30.at.16.15.02.mov
Desktop
Untitled.mov
iOS
Screen.Recording.2023-03-30.at.16.04.44.mov
Android
Screen.Recording.2023-03-30.at.16.10.55.mov

@sobitneupane
Copy link
Contributor

@sobitneupane updated, let me know if i need to add more.

Thanks @getusha
Can you also update the screen recordings covering the latest test steps.

@getusha
Copy link
Contributor Author

getusha commented Mar 30, 2023

Screenshots/Videos

Web
Screen.Recording.2023-03-30.at.4.00.08.AM.mov
Mobile Web - Chrome
Screen.Recording.2023-03-30.at.4.13.48.AM.mov
Mobile Web - Safari
Screen.Recording.2023-03-30.at.4.24.44.AM.mov
Desktop
Screen.Recording.2023-03-30.at.4.29.20.AM.mov
iOS
Screen.Recording.2023-03-30.at.4.50.24.AM.1.mov
Android
Screen.Recording.2023-03-30.at.5.16.23.AM.mov

@getusha
Copy link
Contributor Author

getusha commented Mar 30, 2023

@sobitneupane Just updated the screen recordings.

Copy link
Contributor

@sobitneupane sobitneupane left a comment

Choose a reason for hiding this comment

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

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 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 correct English and 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 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.

@techievivek
Copy link
Contributor

@getusha There doesn't seem to be any video where we are switching from offline -> online or vice-versa, can you update the PR with video including those cases? Thanks

Copy link
Contributor

@techievivek techievivek 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, please add some videos transitioning from offline->online and vice-versa. Thanks

@getusha
Copy link
Contributor Author

getusha commented Mar 31, 2023

@techievivek are you suggesting switching from offline to online to show if the actions/message were successful?

@getusha
Copy link
Contributor Author

getusha commented Mar 31, 2023

Switching from online to offline to perform the actions while the chat loading is quite difficult since it will load the chat quickly and no longer showing the Skeleton view.

@situchan
Copy link
Contributor

Switching from online to offline to perform the actions while the chat loading is quite difficult since it will load the chat quickly and no longer showing the Skeleton view.

This is easy to reproduce. Especially login with expensifail account which is high traffic on android with slow network

@techievivek
Copy link
Contributor

@getusha

Switching from online to offline to perform the actions while the chat loading
Can you not throttle your network connection?

Screenshot 2023-03-31 at 12 18 43 PM

@getusha
Copy link
Contributor Author

getusha commented Mar 31, 2023

@situchan @techievivek thank you!
I will record the video and update performing the actions offline and making it online.
It seems like the backend is down, will update and let you know once it's back. 🙇

@getusha
Copy link
Contributor Author

getusha commented Mar 31, 2023

Screenshots/Videos

Web
Screen.Recording.2023-03-31.at.7.12.24.AM.mov
Mobile Web - Chrome
Screen.Recording.2023-03-31.at.7.19.03.AM.mov
Mobile Web - Safari
Screen.Recording.2023-03-31.at.7.25.49.AM.mov
Desktop
Screen.Recording.2023-03-31.at.8.21.33.AM.mov
iOS
Screen-Recording-2023-03-31-at-9.1.mp4
Android
Screen-Recording-2023-03-31-at-8.1.mp4

@getusha
Copy link
Contributor Author

getusha commented Mar 31, 2023

@techievivek just updated with the recordings.
can we get this today? thank you!

Copy link
Contributor

@techievivek techievivek 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 to me, thanks for the additional screen recordings.

@techievivek techievivek merged commit 265f8bf into Expensify:main Mar 31, 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

OSBotify commented Apr 3, 2023

🚀 Deployed to staging by https://github.com/techievivek in version: 1.2.94-0 🚀

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

@johnmlee101
Copy link
Contributor

Possible Regression: #16908

@OSBotify
Copy link
Contributor

OSBotify commented Apr 5, 2023

🚀 Deployed to production by https://github.com/thienlnam in version: 1.2.94-3 🚀

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.

7 participants