Migrate BaseReportActionContextMenu.js to fc component. by vadymbokatov · Pull Request #23934 · Expensify/App

vadymbokatov · 2023-07-31T16:18:20Z

Details

Migrated BaseReportActionContextMenu.js to fc component.

Fixed Issues

$ #16259
PROPOSAL:

Tests

Verify that no errors appear in the JS console
Verify that BaseReportActionContextMenu is working correctly.
- Open the app authenticated.
- Open chat history with anyone.
- Hover or right click text in chat history.
- Check all the actions are working correctly like emojis, reply in thread, make as read, edit comment and delete comment.

Offline tests

QA Steps

Same as test steps

PR Author Checklist

Screenshots/Videos

Web

Screen.Recording.2023-08-01.at.21.10.35.mov

Mobile Web - Chrome

Screen.Recording.2023-08-01.at.21.16.36.mov

Mobile Web - Safari

Screen.Recording.2023-08-01.at.21.13.40.mov

Desktop

Screen.Recording.2023-08-01.at.00.49.56.mov

iOS

Screen.Recording.2023-08-01.at.00.38.17.mov

Android

Screen.Recording.2023-08-01.at.00.45.19.mov

melvin-bot · 2023-07-31T16:18:25Z

@robertKozik 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]

robertKozik · 2023-08-01T12:47:49Z

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

android.-.web.mov

Mobile Web - Safari

iOS.-.web.MP4

Desktop

desktop.mov

iOS

iOS.-.native.mov

Android

android.-.native.mov

robertKozik · 2023-08-01T12:49:26Z

Hi @vadymbokatov! Would it be possible to update the test steps? Currently, I can't see any, but we need them to check all the checkboxes. Thanks so much!

vadymbokatov · 2023-08-01T13:03:34Z

@robertKozik Updated. Thank you

robertKozik

One styling concern

robertKozik · 2023-08-01T13:14:03Z

-                            if (__DEV__ && (contextAction.text != null || contextAction.icon != null)) {
-                                throw new Error('Dev error: renderContent() and text/icon cannot be used together.');
-                            }
+function BaseReportActionContextMenu(props) {


Can we destructure the props here?
As per this line of STYLE.md:
Always use destructuring to get prop values. Destructuring is necessary to assign default values to props.

@robertKozik I tried to use destructuring to get prop values but I am getting this lint errors. It requires to use default props.

Can't we assign default values to make lint happy?

I think, we can't.

I checked other fc components but they don't use destructuring as well.

Okay, got it, thank you

robertKozik

Tests well, let's push it forward

OSBotify · 2023-08-02T22:27:00Z

✋ 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-08-03T17:41:34Z

🚀 Deployed to staging by https://github.com/marcaaron in version: 1.3.50-0 🚀

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

OSBotify · 2023-08-07T18:29:54Z

🚀 Deployed to production by https://github.com/puneetlath in version: 1.3.50-3 🚀

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

OSBotify · 2023-08-07T18:57:07Z

🚀 Deployed to staging by https://github.com/marcaaron in version: 1.3.51-0 🚀

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

OSBotify · 2023-08-09T08:46:15Z

🚀 Deployed to production by https://github.com/Julesssss in version: 1.3.51-2 🚀

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

Migrate baseReportActionContextMenu.js to fc component.

371f399

vadymbokatov requested a review from a team as a code owner July 31, 2023 16:18

melvin-bot bot requested review from robertKozik and removed request for a team July 31, 2023 16:18

vadymbokatov mentioned this pull request Jul 31, 2023

[$250] Migrate BaseReportActionContextMenu.js to function component #16259

Closed

1 task

robertKozik suggested changes Aug 1, 2023

View reviewed changes

robertKozik approved these changes Aug 2, 2023

View reviewed changes

melvin-bot bot requested a review from marcaaron August 2, 2023 14:53

marcaaron approved these changes Aug 2, 2023

View reviewed changes

marcaaron merged commit 15abe02 into Expensify:main Aug 2, 2023

OSBotify mentioned this pull request Aug 3, 2023

Deploy Checklist: New Expensify 2023-08-03 #24121

Closed

86 tasks

OSBotify mentioned this pull request Aug 7, 2023

Deploy Checklist: New Expensify 2023-08-07 #24230

Closed

98 tasks

situchan mentioned this pull request Aug 10, 2023

[HOLD for payment 2023-10-02] [$1000] Web- Action menu - Unable to navigate options in Action menu using Arrow keys #23280

Closed

6 tasks

Conversation

vadymbokatov commented Jul 31, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Jul 31, 2023

Uh oh!

robertKozik commented Aug 1, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

robertKozik commented Aug 1, 2023

Uh oh!

vadymbokatov commented Aug 1, 2023

Uh oh!

robertKozik left a comment

Choose a reason for hiding this comment

Uh oh!

robertKozik Aug 1, 2023

Choose a reason for hiding this comment

Uh oh!

vadymbokatov Aug 1, 2023

Choose a reason for hiding this comment

Uh oh!

robertKozik Aug 1, 2023

Choose a reason for hiding this comment

Uh oh!

vadymbokatov Aug 1, 2023

Choose a reason for hiding this comment

Uh oh!

vadymbokatov Aug 1, 2023

Choose a reason for hiding this comment

Uh oh!

robertKozik Aug 2, 2023

Choose a reason for hiding this comment

Uh oh!

robertKozik left a comment

Choose a reason for hiding this comment

Uh oh!

OSBotify commented Aug 2, 2023

Uh oh!

OSBotify commented Aug 3, 2023

Uh oh!

OSBotify commented Aug 7, 2023

Uh oh!

OSBotify commented Aug 7, 2023

Uh oh!

OSBotify commented Aug 9, 2023

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

vadymbokatov commented Jul 31, 2023 •

edited

Loading

robertKozik commented Aug 1, 2023 •

edited

Loading