-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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 for payment 2024-07-24] [$250] Chat - Copying a message with a reply doesn't refocus on the composer #44078
Comments
Triggered auto assignment to @garrettmknight ( |
@garrettmknight 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 |
We think that this bug might be related to #vip-vsp |
Job added to Upwork: https://www.upwork.com/jobs/~0132ecedb1bbac288c |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.The app doesn't focus on the composer after copying What is the root cause of that problem?This only happens in case the URL points to a report action (i.e. After pressing the context menu item, we refocus the composer. But we early return if the active route is not the current report route (i.e. App/src/libs/ReportActionComposeFocusManager.ts Lines 34 to 37 in e9dc2ef
But we didn't cover the case of report action linking. What changes do you think we should make in order to solve the problem?Include the case of report action linking as well: if (!Navigation.isActiveRoute(ROUTES.REPORT_WITH_ID.getRoute(Navigation.getTopmostReportId() ?? '-1', Navigation.getTopmostReportActionId()))) {
return;
} |
ProposalPlease re-state the problem that we are trying to solve in this issue.The app doesn't focus on the composer after copying What is the root cause of that problem?When we copy a message, we have a callback to focus to composer here.
But in the case the URL of report screen has App/src/libs/ReportActionComposeFocusManager.ts Lines 35 to 36 in 633e708
What changes do you think we should make in order to solve the problem?This also doesn't work when we open report as a RHP from search screen. So we should check if the current route is the report screen or report screen RHP, we will re-focus on the composer. We can do like this (Here just an example implementation, we can optimize it or have other way with this idea in the PR phrase).
App/src/libs/ReportActionComposeFocusManager.ts Lines 35 to 36 in 633e708
What alternative solutions did you explore? (Optional) |
@gijoe0295 your root cause makes sense. What would |
@rushatgabhane it would return |
@gijoe0295's proposal LGTM |
Triggered auto assignment to @luacmartins, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
@rushatgabhane This proposal doesn't work when we do the same step in Search_Report screen. This report has another route pattern. |
Screen.Recording.2024-06-21.at.18.00.43.mov |
@rushatgabhane can you check the latest comment above? Is the selected proposal still good? |
@garrettmknight, @luacmartins, @rushatgabhane Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@rushatgabhane bump on this one when you get a chance. |
@nkdengineer yeah your proposal is iterating on the same root cause for another page. Which we wouldn't have found unless you had mentioned it |
@gijoe0295's proposal fixes this issue, but @nkdengineer has identified another page that has this issue too. @luacmartins who should we hire? |
I think we can hire @gijoe0295 since they pointed out the correct RCA for the issue. We can split the bounty 50/50 between @gijoe0295 and @nkdengineer since they both contributed to the fix. |
📣 @gijoe0295 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
📣 @nkdengineer 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
PR on production |
@garrettmknight @nkdengineer @rushatgabhane Before summarizing payment, I want to raise a discussion on the split share between me and the other contributor (50:50 currently).
IMO @nkdengineer contribution here is obviously valuable (I'm grateful for that) but comparing to my efforts to investigate the final working solution, the 50:50 split seems not convincing. Therefore I suggest a 75:25 share for me and @nkdengineer. What do you all think about it? I'm open for discussions! |
Hey @gijoe0295 I appreciate your work on this. Since you were the one who actually coded it, I'm open to giving you 75% payment AND giving @nkdengineer 50%. |
Payment Summary:
@rushatgabhane can you complete the checklist and request payment when you have? |
Triggered auto assignment to @stephanieelliott ( |
@stephanieelliott just handing this one off while I'm OOO next week - only awaiting the checklist. If it doesn't get done by the time I'm back I'll pick back up. Thanks! |
|
$250 approved for @rushatgabhane |
Issue for new test case here! https://github.com/Expensify/Expensify/issues/new |
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.86-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: N/A
Email or phone of affected tester (no customers): abebemiherat@gmail.com
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
The app should focus on the composer after copying
Actual Result:
The app doesn't focus on the composer after copying
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6519290_1718880662989.Screen_Recording_2024-06-20_at_3.47.23_AM.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @stephanieelliottThe text was updated successfully, but these errors were encountered: