-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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-05-22] [LOW] Distance: PHASE 2 CLEANUP - Refactor navigation among screens related to money request features #29107
Comments
Job added to Upwork: https://www.upwork.com/jobs/~01b453df445e7dd962 |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @ntdiary ( |
This is still mostly on HOLD while I work on phase 1. I updated this issue yesterday to change the date of the last time I checked the files for change, which I also did yesterday. |
This issue has not been updated in over 15 days. @tgolen, @ntdiary eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
Hi, I will migrate it
|
Triggered auto assignment to @chiragsalian, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
Triggered auto assignment to @amyevans, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
Triggered auto assignment to @francoisl, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
Sorry about that. The PR approval automation didn't work as expected |
@s77rt so @francoisl, @chiragsalian, and I should unassign? Just want to double check since I'm unclear where the trigger even came from 😅 |
@chiragsalian should stay assigned. You and @francoisl can unassign PS: The trigger came from PR approval |
I was able to merge that PR this morning, so I will go ahead and close this issue out. Thanks for all the help with this!! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.73-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-05-22. 🎊 For reference, here are some details about the assignees on this issue:
|
In #26538 Most of the changes were made by adding new components. This eliminated a lot of conflicting headaches from people working on existing components.
Phase 2 is all about removing the original components and any of the duplicated efforts. The tasks that need to be done as part of this issue are:
iou/ReceiptSelector
and copy any changes since Nov 27 intoIOURequestStepScan/
WaypointEditor.js
and copy any changes since Nov 27 intoIOURequestStepWaypoint.js
MoneyRequestConfirmationList.js
and copy any changes since Nov 27 intoMoneyTemporaryForRefactorRequestConfirmationList.js
#39559ROUTES.ts
and removeMONEY_REQUEST_*
routes, remove "create" from the front of the routeslinkgingConfig.js
and removeMoney_Request*
screensModalStackNavigators.js
remove oldMoney_Request*
componentsIOU.js
and remove_temporaryForRefactor
from the name of any methodsIOU.js
and removestartMoneyRequest()
method and renamestartMoneeRequest()
tostartMoneyRequest()
IOU.js
and removecreateDistanceRequest()
method and userequestMoneyFromDistance()
everywhereONYXKEYS.IOU
EditRequestPage
EditSplitBillPage
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: