fix: Not here page opens when opening distance receipt from another workspace #50546

nkdengineer · 2024-10-10T09:33:09Z

Details

Fixed Issues

$ #50107
PROPOSAL: #50107 (comment)

Tests

Create two workspaces.
Submit a distance expense in the first workspace chat.
Submit the same distance expense in the second workspace chat.
Submit another expense to the second workspace chat (as we cannot review duplicates when there is only one expense).
Go to transaction thread of the second expense in Step 4.
Click Review duplicates.
Click on the second distance expense preview (to make Keep this one button appear).
8 . Click on the receipt on the confirmation page.
Verify that: The receipt opens without issue.

Verify that no errors appear in the JS console

Offline tests

same as above

QA Steps

same as above

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

android.mov

Android: mWeb Chrome

android-mweb.mov

iOS: Native

ios.mov

iOS: mWeb Safari

ios-mweb.mov

MacOS: Chrome / Safari

web.mov

MacOS: Desktop

desktop.mov

…orkspace

melvin-bot · 2024-10-10T16:39:14Z

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

rojiphil

@nkdengineer Thanks for the PR. I have left few comments. Please have a look.

src/ROUTES.ts

rojiphil · 2024-10-11T12:00:30Z

src/components/ReportActionItem/MoneyRequestView.tsx

@@ -75,7 +77,7 @@ const getTransactionID = (report: OnyxEntry<OnyxTypes.Report>, parentReportActio
    return originalMessage?.IOUTransactionID ?? -1;
 };

-function MoneyRequestView({report, shouldShowAnimatedBackground, readonly = false, updatedTransaction}: MoneyRequestViewProps) {
+function MoneyRequestView({report, shouldShowAnimatedBackground, readonly = false, updatedTransaction, isFromReviewDuplicates}: MoneyRequestViewProps) {


Let's set isFromReviewDuplicates to false by default as that's neater.

src/components/ReportActionItem/ReportActionItemImage.tsx

nkdengineer · 2024-10-14T07:55:13Z

@rojiphil Thanks for your review, i updated, please check again

rojiphil · 2024-10-14T17:20:00Z

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 either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- 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 UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design 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

MacOS: Chrome / Safari

50546-web-safari-001.mp4

MacOS: Desktop

50546-desktop-001.mp4

iOS: mWeb Safari

50546-mweb-safari-001.mp4

Android: Native

50546-android-native-001.mp4

Android: mWeb Chrome

50546-mweb-chrome-001.mp4

iOS: Native

50546-ios-native-001.mp4

rojiphil

@nkdengineer Thanks for the updated PR. I have left some NAB comments. Please have a look.

@pecanoro Code LGTM and works well too.
Over to you for review. Thanks.

src/components/ReportActionItem/MoneyRequestView.tsx

src/components/ReportActionItem/ReportActionItemImage.tsx

nkdengineer · 2024-10-15T07:15:26Z

@rojiphil i updated, please check again

rojiphil · 2024-10-15T12:48:36Z

i updated, please check again

LGTM. Thanks. I have already approved.
@pecanoro All yours. Thanks

OSBotify · 2024-10-15T15:33:43Z

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

github-actions · 2024-10-17T01:59:38Z

🚀 Deployed to staging by https://github.com/pecanoro in version: 9.0.50-0 🚀

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

github-actions · 2024-10-18T18:48:28Z

🚀 Deployed to production by https://github.com/marcaaron in version: 9.0.50-8 🚀

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

nkdengineer added 2 commits October 10, 2024 16:32

fix: Not here page opens when opening distance receipt from another w…

9f8e8c5

…orkspace

minor change

519561d

nkdengineer marked this pull request as ready for review October 10, 2024 16:39

nkdengineer requested a review from a team as a code owner October 10, 2024 16:39

melvin-bot bot requested a review from rojiphil October 10, 2024 16:39

melvin-bot bot removed the request for review from a team October 10, 2024 16:39

rojiphil reviewed Oct 11, 2024

View reviewed changes

pecanoro self-requested a review October 11, 2024 15:30

fix: add default value to isFromReviewDuplicates

01a9daa

rojiphil approved these changes Oct 14, 2024

View reviewed changes

src/components/ReportActionItem/MoneyRequestView.tsx Show resolved Hide resolved

src/components/ReportActionItem/ReportActionItemImage.tsx Show resolved Hide resolved

add comment

ef00285

pecanoro approved these changes Oct 15, 2024

View reviewed changes

pecanoro merged commit 2d9a28f into Expensify:main Oct 15, 2024
16 checks passed

github-actions bot mentioned this pull request Oct 17, 2024

Deploy Checklist: New Expensify 2024-10-17 #50969

Closed

90 tasks

Pujan92 mentioned this pull request Oct 17, 2024

[HOLD for payment 2024-10-29] [HOLD for payment 2024-10-25] [$250] Receipt - Receipt 3dots menu doesn't show options to replace and delete receipt #50980

Closed

8 tasks

melvin-bot bot mentioned this pull request Oct 18, 2024

[HOLD for payment 2024-10-25] [$250] [Dupe detect] Not here page opens when opening distance receipt from another workspace #50107

Closed

6 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix: Not here page opens when opening distance receipt from another workspace #50546

fix: Not here page opens when opening distance receipt from another workspace #50546

nkdengineer commented Oct 10, 2024 •

edited

Loading

melvin-bot bot commented Oct 10, 2024

rojiphil left a comment

rojiphil Oct 11, 2024

nkdengineer commented Oct 14, 2024

rojiphil commented Oct 14, 2024

rojiphil left a comment

nkdengineer commented Oct 15, 2024

rojiphil commented Oct 15, 2024

OSBotify commented Oct 15, 2024

github-actions bot commented Oct 17, 2024

github-actions bot commented Oct 18, 2024

fix: Not here page opens when opening distance receipt from another workspace #50546

fix: Not here page opens when opening distance receipt from another workspace #50546

Conversation

nkdengineer commented Oct 10, 2024 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Oct 10, 2024

rojiphil left a comment

Choose a reason for hiding this comment

rojiphil Oct 11, 2024

Choose a reason for hiding this comment

nkdengineer commented Oct 14, 2024

rojiphil commented Oct 14, 2024

Reviewer Checklist

Screenshots/Videos

rojiphil left a comment

Choose a reason for hiding this comment

nkdengineer commented Oct 15, 2024

rojiphil commented Oct 15, 2024

OSBotify commented Oct 15, 2024

github-actions bot commented Oct 17, 2024

github-actions bot commented Oct 18, 2024

nkdengineer commented Oct 10, 2024 •

edited

Loading