Update Row Hover Color to Product300 and update Card / ReportPreview Hover Color #33097

grgia · 2023-12-14T17:46:27Z

Details

Hovering over a report action item now uses color product300. The cardBG remains the same color on Hover.

Fixed Issues

$ #33078
PROPOSAL:

Tests

Verify that no errors appear in the JS console
Applied this diff for the reportPreview with default button

diff --git a/src/components/ReportActionItem/ReportPreview.js b/src/components/ReportActionItem/ReportPreview.js
index aa3c02b76f..a6daa54bd4 100644
--- a/src/components/ReportActionItem/ReportPreview.js
+++ b/src/components/ReportActionItem/ReportPreview.js
@@ -272,7 +272,7 @@ function ReportPreview(props) {
                                 </View>
                             </View>
                         )}
-                        {shouldShowSettlementButton && (
+                        {false && (
                             <SettlementButton
                                 currency={props.iouReport.currency}
                                 policyID={props.policyID}
@@ -294,10 +294,10 @@ function ReportPreview(props) {
                                 }}
                             />
                         )}
-                        {shouldShowSubmitButton && (
+                        {true && (
                             <Button
                                 medium
-                                success={props.chatReport.isOwnPolicyExpenseChat}
+                                success={false}
                                 text={translate('common.submit')}
                                 style={styles.mt3}
                                 onPress={() => IOU.submitReport(props.iouReport)}

opened a Workspace Report containing a ReportPreview
visual QA

Offline tests

QA Steps

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

melvin-bot · 2023-12-14T18:27:22Z

@fedirjh Please 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]

fedirjh · 2023-12-18T01:22:19Z

Screenshots/Videos

Android: Native

CleanShot.2023-12-18.at.02.11.21.mp4

CleanShot.2023-12-18.at.02.14.09.mp4

Android: mWeb Chrome

CleanShot.2023-12-18.at.01.31.26.mp4

CleanShot.2023-12-18.at.01.35.50.mp4

iOS: Native

CleanShot.2023-12-18.at.01.02.51.mp4

CleanShot.2023-12-18.at.01.03.47.mp4

iOS: mWeb Safari

CleanShot.2023-12-18.at.01.21.23.mp4

CleanShot.2023-12-18.at.01.22.23.mp4

MacOS: Chrome / Safari

MacOS: Desktop

fedirjh · 2023-12-18T01:37:31Z

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

fedirjh

LGTM

hayata-suenaga

👍

OSBotify · 2023-12-19T02:44:57Z

🚀 Deployed to staging by https://github.com/hayata-suenaga in version: 1.4.14-0 🚀

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

OSBotify · 2023-12-19T03:48:18Z

🚀 Deployed to staging by https://github.com/hayata-suenaga in version: 1.4.14-0 🚀

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

OSBotify · 2023-12-21T05:15:53Z

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.4.14-6 🚀

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

change reportActionItem hover color and card hover color

84f5d04

grgia self-assigned this Dec 14, 2023

grgia added 2 commits December 14, 2023 10:20

use existing theme.hoverComponentBG key

debced7

fix avatar border

de409fa

grgia changed the title ~~change reportActionItem hover color and card hover color~~ Update Row Hover Color to Product300 and update Card / ReportPreview Hover Color Dec 14, 2023

grgia marked this pull request as ready for review December 14, 2023 18:27

grgia requested a review from a team as a code owner December 14, 2023 18:27

melvin-bot bot requested review from fedirjh and removed request for a team December 14, 2023 18:27

remove old key

b43d4e6

fedirjh approved these changes Dec 18, 2023

View reviewed changes

melvin-bot bot requested a review from hayata-suenaga December 18, 2023 01:40

hayata-suenaga approved these changes Dec 18, 2023

View reviewed changes

hayata-suenaga merged commit 771ec1e into main Dec 18, 2023
16 checks passed

hayata-suenaga deleted the georgia-fixLightModeColors branch December 18, 2023 21:53

github-actions bot mentioned this pull request Dec 19, 2023

Deploy Checklist: New Expensify 2023-12-19 #33264

Closed

98 tasks

melvin-bot bot mentioned this pull request Dec 21, 2023

[HOLD for payment 2023-12-28] [Theme Switching] 🎨🐛 Draft Card Preview Hover Color Is Incorrect in Both Themes #33078

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update Row Hover Color to Product300 and update Card / ReportPreview Hover Color #33097

Update Row Hover Color to Product300 and update Card / ReportPreview Hover Color #33097

grgia commented Dec 14, 2023 •

edited

Loading

melvin-bot bot commented Dec 14, 2023

fedirjh commented Dec 18, 2023

fedirjh commented Dec 18, 2023 •

edited

Loading

fedirjh left a comment

hayata-suenaga left a comment

OSBotify commented Dec 19, 2023

OSBotify commented Dec 19, 2023

OSBotify commented Dec 21, 2023

Update Row Hover Color to Product300 and update Card / ReportPreview Hover Color #33097

Update Row Hover Color to Product300 and update Card / ReportPreview Hover Color #33097

Conversation

grgia commented Dec 14, 2023 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Dec 14, 2023

fedirjh commented Dec 18, 2023

Screenshots/Videos

fedirjh commented Dec 18, 2023 • edited Loading

Reviewer Checklist

fedirjh left a comment

Choose a reason for hiding this comment

hayata-suenaga left a comment

Choose a reason for hiding this comment

OSBotify commented Dec 19, 2023

OSBotify commented Dec 19, 2023

OSBotify commented Dec 21, 2023

grgia commented Dec 14, 2023 •

edited

Loading

fedirjh commented Dec 18, 2023 •

edited

Loading