Hidden reveal message button when editing message #20737

dukenv0307 · 2023-06-14T03:49:05Z

Details

Hidden reveal message button when editing message

Fixed Issues

$ #20306
PROPOSAL: #20306 (comment)

Tests

Login with user A
In another device log in with user B
From user A, send a message to user B
From user B, flags as offensive to hidden the message
From user A, click on reveal message button to show the message
From user A, edit the message
Verify that reveal message button is hidden when editing message
After updated the message, verify that the message still shows

Verify that no errors appear in the JS console

Offline tests

Same above

QA Steps

Login with user A
In another device log in with user B
From user A, send a message to user B
From user B, flags as offensive to hidden the message
From user A, click on reveal message button to show the message
From user A, edit the message
Verify that reveal message button is hidden when editing message
After updated the message, verify that the message still shows

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Web

Screencast.from.14-06-2023.11.00.05.webm

Mobile Web - Chrome

Record_2023-06-14-11-01-08.mp4

Mobile Web - Safari

Screen.Recording.2023-06-14.at.11.08.51.mp4

Desktop

Screen.Recording.2023-06-14.at.11.17.41.1.mp4

iOS

Screen.Recording.2023-06-14.at.11.40.13.1.mp4

Android

20306.mp4

melvin-bot · 2023-06-14T04:52:25Z

@robertjchen @aimane-chnaif 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]

aimane-chnaif · 2023-06-14T04:59:20Z

src/pages/home/report/ReportActionItem.js

@@ -134,7 +135,10 @@ function ReportActionItem(props) {
            setIsHidden(true);
        }
        setModerationDecision(latestDecision.decision);
-    }, [props.action.message, props.action.actionName]);
+
+        // props.action.message doesn't need to be a dependency, we only need to check the change of props.action.message[0].moderationDecisions


I don't think this comment is necessary

@aimane-chnaif I saw that all disabled eslint react hooks in the production have a comment to explain why disable it so I add a comment in here.

aimane-chnaif · 2023-06-14T05:50: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 / 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

web.mov

Mobile Web - Chrome

mchrome.mov

Mobile Web - Safari

msafari.mov

Desktop

desktop.mov

iOS

ios.mov

Android

android.mov

aimane-chnaif

@robertjchen LGTM 🎉

robertjchen · 2023-06-14T05:52:20Z

Thanks for the review and test! 👍

OSBotify · 2023-06-14T05:56:37Z

✋ 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 · 2023-06-14T21:25:53Z

🚀 Deployed to staging by https://github.com/robertjchen in version: 1.3.28-0 🚀

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

OSBotify · 2023-06-16T18:41:00Z

🚀 Deployed to production by https://github.com/AndrewGable in version: 1.3.28-5 🚀

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

dukenv0307 added 3 commits June 14, 2023 10:41

Hidden reveal message button when editing message

e44d211

fix lint

0825c4b

edit comment

3b46dd7

dukenv0307 marked this pull request as ready for review June 14, 2023 04:52

dukenv0307 requested a review from a team as a code owner June 14, 2023 04:52

melvin-bot bot requested review from aimane-chnaif and robertjchen and removed request for a team June 14, 2023 04:52

aimane-chnaif reviewed Jun 14, 2023

View reviewed changes

aimane-chnaif approved these changes Jun 14, 2023

View reviewed changes

robertjchen approved these changes Jun 14, 2023

View reviewed changes

robertjchen merged commit 23978e4 into Expensify:main Jun 14, 2023

OSBotify mentioned this pull request Jun 14, 2023

Deploy Checklist: New Expensify 2023-06-14 #20782

Closed

hungvu193 mentioned this pull request Jun 15, 2023

[HOLD for payment 2023-07-12] [$1000] Web - Chat - Flagged attachment are collapsed when reacted with emojis #20810

Closed

6 tasks

melvin-bot bot mentioned this pull request Jun 16, 2023

[HOLD for payment 2023-06-23] [$1000] Reveal message does not work when editing comment #20306

Closed

6 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Hidden reveal message button when editing message #20737

Hidden reveal message button when editing message #20737

dukenv0307 commented Jun 14, 2023 •

edited

Loading

melvin-bot bot commented Jun 14, 2023

aimane-chnaif Jun 14, 2023

dukenv0307 Jun 14, 2023

aimane-chnaif commented Jun 14, 2023

aimane-chnaif left a comment

robertjchen commented Jun 14, 2023

OSBotify commented Jun 14, 2023

OSBotify commented Jun 14, 2023

OSBotify commented Jun 16, 2023

Hidden reveal message button when editing message #20737

Hidden reveal message button when editing message #20737

Conversation

dukenv0307 commented Jun 14, 2023 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Jun 14, 2023

aimane-chnaif Jun 14, 2023

Choose a reason for hiding this comment

dukenv0307 Jun 14, 2023

Choose a reason for hiding this comment

aimane-chnaif commented Jun 14, 2023

Reviewer Checklist

Screenshots/Videos

aimane-chnaif left a comment

Choose a reason for hiding this comment

robertjchen commented Jun 14, 2023

OSBotify commented Jun 14, 2023

OSBotify commented Jun 14, 2023

OSBotify commented Jun 16, 2023

dukenv0307 commented Jun 14, 2023 •

edited

Loading