Skip to content

Modify Avatar to add imageStyles when image error#12908

Merged
sketchydroide merged 8 commits into
Expensify:mainfrom
markarmanus:main
Nov 24, 2022
Merged

Modify Avatar to add imageStyles when image error#12908
sketchydroide merged 8 commits into
Expensify:mainfrom
markarmanus:main

Conversation

@markarmanus

@markarmanus markarmanus commented Nov 21, 2022

Copy link
Copy Markdown
Contributor

Details

Simply the avatar component was applying the style to the Image component. But not the Icon component. The icon component is used when This.state.imageError is true. which could happen when there is a problem loading the avatar image. To solive it i wrap the Icon in a View and apply the styles to it.

Fixed Issues

$ #12645
$ #12645 (comment)

Tests

  1. Force the component to be in the error state by setting this.state.imageError to always true
  2. Run through the entire app on all platforms confirming all locations and uses of the Avatar component still work.
  • Verify that no errors appear in the JS console

Offline tests

The changes are only applied when the app is offline. So for offline tests simply run through the QA steps below to confirm the component styling is still proper while offline.

QA Steps

The test here could be done by having Airplane mode on. That seems to trigger the altenrative version of the component where the issue existed. So to test the app we need to check the component is still working properly (only style changes applied) in the entire app on all platforms on Airplane mode.

  1. Turn on Airplane mode
  2. Confirm the Avatar still looks good in all screens on all platforms

Note: because if you have airplane mode you might not be able to access some pages (i.e you need internet to login) You might have to toggle between on/off for airplane mode a few times while testing.

  • 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:

    • 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 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 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.

  • 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

  • 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 expected offline behavior are in the Offline steps 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 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 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:
    • iOS / native
    • Android / native
    • iOS / Safari
    • Android / Chrome
    • MacOS / Chrome
    • 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 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 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
  • 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 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.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots

Web

Screen.Recording.2022-11-21.at.9.38.03.PM.mp4

Mobile Web - Chrome

Screen.Recording.2022-11-21.at.10.57.44.PM.mp4

Mobile Web - Safari

Screen.Recording.2022-11-21.at.10.34.22.PM.mp4

Desktop

Screen.Recording.2022-11-21.at.9.31.42.PM.mp4

iOS

Screen.Recording.2022-11-21.at.11.40.02.PM.mp4

Android

Screen.Recording.2022-11-21.at.10.23.31.PM.mov

@markarmanus markarmanus requested a review from a team as a code owner November 21, 2022 23:10
@melvin-bot melvin-bot Bot requested review from parasharrajat and sketchydroide and removed request for a team November 21, 2022 23:10
@melvin-bot

melvin-bot Bot commented Nov 21, 2022

Copy link
Copy Markdown

@sketchydroide @parasharrajat 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]

@github-actions

github-actions Bot commented Nov 21, 2022

Copy link
Copy Markdown
Contributor

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

@markarmanus

Copy link
Copy Markdown
Contributor Author

I have read the CLA Document and I hereby sign the CLA

@markarmanus

Copy link
Copy Markdown
Contributor Author

recheck

@markarmanus

markarmanus commented Nov 22, 2022

Copy link
Copy Markdown
Contributor Author

If you notice the offline avatar shape change in the videos. Its another bug that is currently being fixed. Here is the issue associated with it
#12713

Took a while to hunt down but i was gonna report it my self.

sketchydroide
sketchydroide previously approved these changes Nov 22, 2022

@sketchydroide sketchydroide left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

looks like what it was agreed

@sketchydroide

Copy link
Copy Markdown
Contributor

@parasharrajat let me know once you are done with review :)

Comment thread src/components/Avatar.js Outdated
@parasharrajat

parasharrajat commented Nov 23, 2022

Copy link
Copy Markdown
Member

Now, we just need to filter the extra background color that is being applied to the icon. It looks a little darker as mentioned in #12645 (comment).

I think it won't be safe to remove the fill condition which sets the offline color. Instead, remove the background from the image style for the new View you added but keep it for the image.

You can apply whatever you think is best. But test it carefully. This is the most used component in the app.

@markarmanus

Copy link
Copy Markdown
Contributor Author

@parasharrajat I just extended the component. Tested it on a few platforms looks good to me.

Comment thread src/components/Avatar.js Outdated
@markarmanus

Copy link
Copy Markdown
Contributor Author

@parasharrajat apologies on the styling. still getting used to the app.

Co-authored-by: Rajat Parashar <parasharrajat@users.noreply.github.com>
@parasharrajat

Copy link
Copy Markdown
Member

image

This does not make sense to me. Could you please add a basic offline test?

  1. Turn the Internet off on the device by _____________.
  2. Open New Chat from ➕ FAB button.
  3. Add a new email that does not exist.
  4. Create Chat.
  5. Chat is created successfully.

etc.

@markarmanus

Copy link
Copy Markdown
Contributor Author

@parasharrajat considering our changes are only applied when this.state.imageError is true Then isnt a better test to set this.state.imageError = true and run through the app. basically testing if all components where using the area of code i changed ?

@parasharrajat

Copy link
Copy Markdown
Member

That is a better test for developers but can QA team change the code on staging? we should write QA steps in a way that a non-technical person is able to test them.

@markarmanus

Copy link
Copy Markdown
Contributor Author

@parasharrajat The steps under the QA section should cover that. as it will be in airplane mode(offline mode)

@markarmanus

Copy link
Copy Markdown
Contributor Author

i updated the offline section to refer the QA section if that helps.

@markarmanus markarmanus requested review from parasharrajat and sketchydroide and removed request for parasharrajat and sketchydroide November 23, 2022 16:53
@parasharrajat

parasharrajat commented Nov 23, 2022

Copy link
Copy Markdown
Member

Screenshots

🔲 iOS / native

Screenshot 2022-11-24 02:28:02

🔲 iOS / Safari

Screenshot 2022-11-23 22:47:11

🔲 MacOS / Desktop

Screenshot 2022-11-23 22:49:50

🔲 MacOS / Chrome

Screenshot 2022-11-23 21:15:06

🔲 Android / Chrome

...

🔲 Android / native

Screenshot 2022-11-24 02:34:04

@markarmanus

Copy link
Copy Markdown
Contributor Author

@parasharrajat is the build issue on ios related to yoga ?

@parasharrajat

Copy link
Copy Markdown
Member

There was cache issue which is resolved now.

@parasharrajat parasharrajat left a comment

Copy link
Copy Markdown
Member

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:
    • iOS / native
    • Android / native
    • iOS / Safari
    • Android / Chrome
    • MacOS / Chrome
    • 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 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 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 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.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

cc: @sketchydroide

🎀 👀 🎀 C+ reviewed

@markarmanus

Copy link
Copy Markdown
Contributor Author

@sketchydroide any updates on the PR ?

@sketchydroide

Copy link
Copy Markdown
Contributor

sorry but you had to wait for me to get back to work :D

@sketchydroide sketchydroide merged commit d0fbcf8 into Expensify:main Nov 24, 2022
@OSBotify

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

🚀 Deployed to staging by @sketchydroide in version: 1.2.32-0 🚀

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by @luacmartins in version: 1.2.32-2 🚀

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by @luacmartins in version: 1.2.32-2 🚀

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.

4 participants