-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[HOLD #39432][$500] Report - Offline deleted message is not struck through #39307
Comments
Triggered auto assignment to @strepanier03 ( |
@strepanier03 FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
ProposalPlease re-state the problem that we are trying to solve in this issue.Message disappears What is the root cause of that problem?What changes do you think we should make in order to solve the problem?When we delete a message that isn't a thread parent message, the current request is included to handle conflicting request and then we merge the App/src/libs/actions/Report.ts Line 1321 in 272b05f
App/src/libs/actions/PersistedRequests.ts Line 40 in 272b05f
What alternative solutions did you explore? (Optional)We should handle merge the optimistic data of the request after we handle conflicting request Lines 67 to 69 in 272b05f
To do that we should move this block after we push the request here |
Raising this internally because I'm finding contradicting expected behavior. |
Okay "greyed out and struck through" is the expected behavior. |
Job added to Upwork: https://www.upwork.com/jobs/~0123d5e156c38fe58b |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @hungvu193 ( |
Hey @roryabraham, I believe this issue is a regression from your recent PR, do you want to fix this as a separate issue or treat it as a regression? Revert PRScreen.Recording.2024-04-04.at.10.22.29.mov |
I'd be happy to fix this in a follow-up, I don't think we should revert this, as the bug(s) I fixed were worse than this one. |
Thanks, @nkdengineer. I'm not convinced by the solution of moving the updating optimisticData after Screen.Recording.2024-04-04.at.13.21.00.mov |
Hello @hungvu193 Can you please hold this issue on another similar issue? Thanks |
Can you please link that similar issue here?
|
Awesome, @strepanier03 let's put this on hold for #39432 |
hold for #39432 |
Still on hold, good to keep pausing. |
Still on HOLD, will resume #39432 as soon as I can |
Thanks Rory! |
still on hold |
Currently on hold. |
VSB is on hold. Thinking of moving this to monthly. |
Moving to monthly for now. |
Going to retest this, it's been quite some time since it was created and tested. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 1.4.58-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4467827
Email or phone of affected tester (no customers): natnael.expensify+3@gmail.com
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
Message should be grayed out, and struck through
Actual Result:
Message disappears
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6431930_1711737045335.Screen_Recording_2024-03-29_at_9.22.11_at_night.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: