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

Dark Mode: Make Menu Icons Green #13109

Merged
merged 1 commit into from
Nov 29, 2022
Merged

Dark Mode: Make Menu Icons Green #13109

merged 1 commit into from
Nov 29, 2022

Conversation

grgia
Copy link
Contributor

@grgia grgia commented Nov 28, 2022

Details

Changes menu buttons to green

Fixed Issues

$ #13104

Tests

  • Verify that no errors appear in the JS console
  • Open all menus (profile, workspace, (+), etc) to ensure icons are correct colors

Offline tests

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

Web image image image image
Mobile Web - Chrome
Screen.Recording.2022-11-28.at.4.04.14.PM.mov
Mobile Web - Safari
Screen.Recording.2022-11-28.at.4.03.01.PM.mov
Desktop
Screen.Recording.2022-11-28.at.3.58.46.PM.mov
iOS
Screen.Recording.2022-11-28.at.4.01.53.PM.mov
Android
Screen.Recording.2022-11-28.at.4.03.29.PM.mov

@grgia grgia self-assigned this Nov 28, 2022
@shawnborton
Copy link
Contributor

Looks good! Can you verify that the green CTA option rows are all good too? Basically these:

image

@grgia
Copy link
Contributor Author

grgia commented Nov 28, 2022

image

image

image

image

@shawnborton
Copy link
Contributor

:chefkiss: perfect, thanks!

@grgia grgia marked this pull request as ready for review November 29, 2022 00:10
@grgia grgia requested a review from a team as a code owner November 29, 2022 00:10
@melvin-bot melvin-bot bot requested review from mollfpr and yuwenmemon and removed request for a team November 29, 2022 00:11
@melvin-bot
Copy link

melvin-bot bot commented Nov 29, 2022

@mollfpr @yuwenmemon 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]

@mollfpr
Copy link
Contributor

mollfpr commented Nov 29, 2022

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.

Screenshots/Videos

Web #13109 Web Settings App Download Links Page #13109 Web Settings About Page #13109 Web Settings Payment Page 2 #13109 Web Settings Payment Page #13109 Web Settings Security Page #13109 Web Settings Profile Page #13109 Web Workspace Connect Bank Account Page #13109 Web Workspace Book Travel Page #13109 Web Workspace Send Invoices Page #13109 Web Workspace Pay Bills Page #13109 Web Workspace Reimbursement Page #13109 Web Workspace Issue Cards Page #13109 Web Workspace Page #13109 Web Settings Page #13109 Web Chat Details Page #13109 Web Chat Popover 2 Hover #13109 Web Chat Popover 2 #13109 Web Chat Popover #13109 Web Floating Button Popover
Mobile Web - Chrome #13109 mWeb:Chrome Workspace Issue Cards Page #13109 mWeb:Chrome Workspace Reimburse Expenses Page #13109 mWeb:Chrome Workspace Pay Bills Page #13109 mWeb:Chrome Workspace Send Invoices Page #13109 mWeb:Chrome Workspace Book Travel Page #13109 mWeb:Chrome Workspace Connect Bank Account Page #13109 mWeb:Chrome Settings Security Page #13109 mWeb:Chrome Add Payment Page #13109 mWeb:Chrome Add Payment Page Popover #13109 mWeb:Chrome Settings About Page #13109 mWeb:Chrome Settings Link Page #13109 mWeb:Chrome Chat Popover 2 #13109 mWeb:Chrome Settings Page
Mobile Web - Safari #13109 mWeb:Safari Settings App Download Links Page #13109 mWeb:Safari Settings About Page #13109 mWeb:Safari Settings Payment Popover #13109 mWeb:Safari Settings Payment Page #13109 mWeb:Safari Settings Security Page #13109 mWeb:Safari Settings Profile Page #13109 mWeb:Safari Workspace Connect Bank Account Page #13109 mWeb:Safari Workspace Book Travel Page #13109 mWeb:Safari Workspace Send Invoices Page #13109 mWeb:Safari Workspace Pay Bills Page #13109 mWeb:Safari Workspace Reimburse Expenses Page #13109 mWeb:Safari Workspace Issue Cards Page #13109 mWeb:Safari Workspace Page #13109 mWeb:Safari Settings Page #13109 mWeb:Safari Chat Details Page #13109 mWeb:Safari Chat Popover 2 #13109 mWeb:Safari Chat Popover #13109 mWeb:Safari LHN Popover
Desktop #13109 Desktop Settings App Download Links Page #13109 Desktop Settings About Page #13109 Desktop Settings Payment Page #13109 Desktop Settings Security Page #13109 Desktop Settings Profile Page #13109 Desktop Workspace Connect Bank Account Page #13109 Desktop Workspace Book Travel Page #13109 Desktop Workspace Send Invoices Page #13109 Desktop Workspace Pay Bills Page #13109 Desktop Workspace Reimburse Expenses Page #13109 Desktop Workspace Issue Cards Page #13109 Desktop Workspace Page #13109 Desktop Settings Page #13109 Desktop Chat Popover 2 Hover #13109 Desktop Chat Popover Hover #13109 Desktop Floathing Button Popover Hover #13109 Desktop Chat Details Page
iOS #13109 iOS Settings App Download Links Page #13109 iOS Settings About Page #13109 iOS Settings Payment Page Popover #13109 iOS Settings Payment Page #13109 iOS Settings Security Page #13109 iOS Settings Profile Page #13109 iOS Workspace Connect Bank Account Page #13109 iOS Workspace Book Travel Page #13109 iOS Workspace Send Invoices Page #13109 iOS Workspace Pay Bills Page #13109 iOS Workspace Reimburse Expenses Page #13109 iOS Workspace Issue Cards Page #13109 iOS Workspace Page #13109 iOS Settings Page #13109 iOS Chat Details Page #13109 iOS Chat Popover 2 #13109 iOS Chat Popover #13109 iOS Floathing Button Popover
Android #13109 Android Settings App Download Links Page #13109 Android Settings About Page #13109 Android Settings Payment Popover #13109 Android Settings Payments Page #13109 Android Settings Security Page #13109 Android Settings Profile Page #13109 Android Workspace Connect Bank Account Page #13109 Android Workspace Book Trave Page #13109 Android Workspace Send Invoices Page #13109 Android Workspace Pay Bills Page #13109 Android Workspace Reimburse Expenses Page #13109 Android Workspace Issue Cards Page #13109 Android Workspace Page #13109 Android Settings Page #13109 Android Chat Details Page #13109 Android Chat Popover 2 #13109 Android Chat Popover #13109 Android Floating Button Popover

Copy link
Contributor

@mollfpr mollfpr left a comment

Choose a reason for hiding this comment

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

LGTM 👍

The checklist and screenshots are #13109 (comment).

🎀 👀 🎀 C+ reviewed!

@yuwenmemon yuwenmemon merged commit 3e47bce into main Nov 29, 2022
@yuwenmemon yuwenmemon deleted the georgia-green-icons branch November 29, 2022 15:28
@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.

@mvtglobally
Copy link

@grgia @shawnborton @yuwenmemon Can you pls confirm if there is anything specific you want us to QA in this PR

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by @yuwenmemon in version: 1.2.34-0 🚀

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

@OSBotify
Copy link
Contributor

OSBotify commented Dec 1, 2022

🚀 Deployed to production by @luacmartins in version: 1.2.34-1 🚀

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.

6 participants