[CP Staging] Fix missing context menu options on money request preview #35285

bernhardoj · 2024-01-28T11:40:21Z

Details

There are some missing context menu options when we long press a money request preview.

Fixed Issues

$ #35244
PROPOSAL: #35244 (comment)

Tests

Same as QA Steps

Verify that no errors appear in the JS console

Offline tests

Same as QA Steps

QA Steps

Create a money request from any user
Press the IOU preview to open the IOU report
Right-click or long-press the money request preview box
Repeat step 3 on the blank space next/previous to the money request preview box
Verify the context menu shown between steps 3 and 4 is the same

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Screen.Recording.2024-01-28.at.19.33.50.mov

Android: mWeb Chrome

Screen.Recording.2024-01-28.at.19.32.04.mov

iOS: Native

Screen.Recording.2024-01-28.at.19.30.04.mov

iOS: mWeb Safari

Screen.Recording.2024-01-28.at.19.28.20.mov

MacOS: Chrome / Safari

Screen.Recording.2024-01-28.at.19.28.54.mov

MacOS: Desktop

Screen.Recording.2024-01-28.at.19.29.20.mov

melvin-bot · 2024-01-28T11:40:25Z

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

bernhardoj · 2024-01-28T11:42:10Z

src/pages/home/report/ReportActionItem.js

@@ -349,6 +349,7 @@ function ReportActionItem(props) {
                    // If originalMessage.iouReportID is set, this is a 1:1 money request in a DM chat whose reportID is props.report.chatReportID
                    chatReportID={originalMessage.IOUReportID ? props.report.chatReportID : props.report.reportID}
                    requestReportID={iouReportID}
+                    reportID={props.report.reportID}


I use my alt solution as it's much easier to understand.

hoangzinh · 2024-01-28T13:25:11Z

@srikarparsi let me know if you need a C+ to review this DB PR

srikarparsi · 2024-01-28T18:45:02Z

Hi @hoangzinh, yes that would be great, thank you

hoangzinh · 2024-01-28T22:45:30Z

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 the PR modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label so the design team can review the changes.
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

Android: Native

Screen.Recording.2024-01-29.at.06.20.37.android.mov

Android: mWeb Chrome

Screen.Recording.2024-01-29.at.06.19.17.android.chrome.mov

iOS: Native

Screen.Recording.2024-01-29.at.06.21.37.ios.mov

iOS: mWeb Safari

Screen.Recording.2024-01-29.at.06.23.14.ios.safari.mov

MacOS: Chrome / Safari

Screen.Recording.2024-01-29.at.06.15.25.web.mov

MacOS: Desktop

Screen.Recording.2024-01-29.at.06.18.28.desktop.mov

hoangzinh

LGTM. Originally I thought about whether we pass duplicated props (chatReportID and reportID) into the component. But after I checked the Report Onyx type:

App/src/types/onyx/Report.ts

Lines 87 to 91 in c5ca9a8

    
           /** ID of the report */ 
        
           reportID: string; 
        
           /** ID of the chat report */ 
        
           chatReportID?: string;

It looks like 2 different things so the alternative solution looks good to me.

srikarparsi

lgtm as well

OSBotify · 2024-01-29T06:55:28Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

…enu-options Fix missing context menu options on money request preview (cherry picked from commit df52347)

OSBotify · 2024-01-29T18:20:01Z

🚀 Cherry-picked to staging by https://github.com/francoisl in version: 1.4.32-5 🚀

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

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

OSBotify · 2024-01-29T19:07:40Z

🚀 Deployed to production by https://github.com/francoisl in version: 1.4.32-5 🚀

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

fix missing context menu options

27271d5

bernhardoj requested a review from a team as a code owner January 28, 2024 11:40

melvin-bot bot removed the request for review from a team January 28, 2024 11:40

melvin-bot bot requested a review from hoangzinh January 28, 2024 11:40

bernhardoj commented Jan 28, 2024

View reviewed changes

hoangzinh approved these changes Jan 28, 2024

View reviewed changes

melvin-bot bot requested a review from srikarparsi January 28, 2024 23:30

srikarparsi approved these changes Jan 29, 2024

View reviewed changes

srikarparsi merged commit df52347 into Expensify:main Jan 29, 2024
16 of 17 checks passed

mountiny changed the title ~~Fix missing context menu options on money request preview~~ [CP Staging] Fix missing context menu options on money request preview Jan 29, 2024

OSBotify pushed a commit that referenced this pull request Jan 29, 2024

Merge pull request #35285 from bernhardoj/fix/35244-missing-context-m…

cbf5994

…enu-options Fix missing context menu options on money request preview (cherry picked from commit df52347)

github-actions bot mentioned this pull request Jan 29, 2024

Deploy Checklist: New Expensify 2024-01-25 #35138

Closed

48 tasks

melvin-bot bot mentioned this pull request Jan 29, 2024

[HOLD for payment 2024-02-07] [$500] IOU - Options missing from context menu when long tap IOU report #35244

Closed

6 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[CP Staging] Fix missing context menu options on money request preview #35285

[CP Staging] Fix missing context menu options on money request preview #35285

bernhardoj commented Jan 28, 2024

melvin-bot bot commented Jan 28, 2024

bernhardoj Jan 28, 2024

hoangzinh commented Jan 28, 2024

srikarparsi commented Jan 28, 2024

hoangzinh commented Jan 28, 2024 •

edited

Loading

hoangzinh left a comment

srikarparsi left a comment

OSBotify commented Jan 29, 2024

OSBotify commented Jan 29, 2024

OSBotify commented Jan 29, 2024

	/** ID of the report */
	reportID: string;

	/** ID of the chat report */
	chatReportID?: string;

[CP Staging] Fix missing context menu options on money request preview #35285

[CP Staging] Fix missing context menu options on money request preview #35285

Conversation

bernhardoj commented Jan 28, 2024

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Jan 28, 2024

bernhardoj Jan 28, 2024

Choose a reason for hiding this comment

hoangzinh commented Jan 28, 2024

srikarparsi commented Jan 28, 2024

hoangzinh commented Jan 28, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

hoangzinh left a comment

Choose a reason for hiding this comment

srikarparsi left a comment

Choose a reason for hiding this comment

OSBotify commented Jan 29, 2024

OSBotify commented Jan 29, 2024

OSBotify commented Jan 29, 2024

hoangzinh commented Jan 28, 2024 •

edited

Loading