-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hide transaction detail and dismiss the edit modal when the request is deleted #24590
Conversation
if (!isDeleted && !isSetted) { | ||
return; | ||
} | ||
Navigation.dismissModal(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With the modal open, If you delete a money request without any message you'll be lead to the "Hmm it's not here" page. Is this intended?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should go to the parent report then
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same logic as when deleting the request without the modal
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When we delete the request if the report of the request has a comment, we don't navigate to parent report. If not, report will be deleted, and then we cannot get the parent report from the report
, so I think dismissing the modal will be fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Besides, if user A is currently in the thread transaction report and on another device user A deletes the request, not found page will also appear.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lets just mimic the same behaviour as if the modal would not be opened (+dismiss it)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In EditRequestPage
, for the case, we delete the request from another device if the report doesn't have any message, report
will be deleted so we cannot get the parentReport
through report
to navigate to parent report.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And the behavior is already the same when we delete the request from another device.
Screencast.from.16-08-2023.07.25.58.webm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seeing as this is the current behaviour on production, perhaps it's out of scope here.
if (!isDeleted && !isSetted) { | ||
return; | ||
} | ||
Navigation.dismissModal(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should go to the parent report then
if (!isDeleted && !isSetted) { | ||
return; | ||
} | ||
Navigation.dismissModal(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same logic as when deleting the request without the modal
Reviewer Checklist
Screenshots/VideosWebMacOS_Chrome_Delete_Request.movMacOS_Chrome_Dismiss_modal.movMobile Web - ChromeAndroid_Chome_Delete_request.movAndroid_Chrome_Dismiss_modal.movMobile Web - SafariiOS_Safari_Delete_request.moviOS_Safari_Dismiss_modal.movDesktopMacOS_Desktop_Delete_request.movMacOS_Desktop_Dismiss_modal.moviOSiOS_Native_Delete_request.moviOS_Native_Dismiss_modal.movAndroidAndroid_Native_Delete_request.movAndroid_Native_Dismiss_modal.mov |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks everyone!
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
@ayazhussain79 Yeah that's expected because for now we are just hiding the transaction detail, which is just a temporary measure. |
🚀 Deployed to staging by https://github.com/mountiny in version: 1.3.55-0 🚀
|
🚀 Deployed to staging by https://github.com/mountiny in version: 1.3.56-0 🚀
|
🚀 Deployed to production by https://github.com/roryabraham in version: 1.3.56-24 🚀
|
@@ -83,6 +83,12 @@ function MoneyRequestView({report, parentReport, shouldShowHorizontalRule, polic | |||
description += ` • ${translate('iou.pending')}`; | |||
} | |||
|
|||
// A temporary solution to hide the transaction detail |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dukenv0307 What was the plan for this once the transaction is added as a prop (which it is now)?
Details
We will hide transaction detail and dismiss the edit modal when the request money is deleted
Fixed Issues
$ #24578
PROPOSAL: #24578 (comment)
Tests
Offline tests
QA Steps
PR Author Checklist
### Fixed Issues
section aboveTests
sectionOffline steps
sectionQA steps
sectiontoggleReport
and notonIconClick
)myBool && <MyComponent />
.src/languages/*
files and using the translation methodWaiting for Copy
label for a copy review on the original GH to get the correct copy.STYLE.md
) were followedAvatar
, I verified the components usingAvatar
are working as expected)/** comment above it */
this
properly so there are no scoping issues (i.e. foronClick={this.submit}
the methodthis.submit
should be bound tothis
in the constructor)this
are necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);
ifthis.submit
is never passed to a component event handler likeonClick
)StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)
)Avatar
is modified, I verified thatAvatar
is working as expected in all cases)ScrollView
component to make it scrollable when more elements are added to the page.main
branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTest
steps.Screenshots/Videos
Web
Screencast.from.16-08-2023.00.04.05.webm
Screencast.from.15-08-2023.23.25.12.webm
Mobile Web - Chrome
Record_2023-08-15-23-30-26.mp4
Record_2023-08-16-00-16-23.mp4
Mobile Web - Safari
Screen.Recording.2023-08-16.at.00.19.41.mov
Screen.Recording.2023-08-16.at.00.22.06.mov
Desktop
Screen.Recording.2023-08-16.at.00.08.53.mov
Screen.Recording.2023-08-16.at.00.09.51.mov
iOS
Screen.Recording.2023-08-16.at.00.39.42.mov
Screen.Recording.2023-08-16.at.00.41.51.mov
Android
24578-1.webm
24578-2.webm