-
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-04-15] [$250] Remove MoneyRequestConfirmPage.js and copy any changes since Nov 27 into IOURequestStepConfirmation.js #34615
Comments
Triggered auto assignment to @adelekennedy ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Remove MoneyRequestConfirmPage.js and copy any changes since Nov 27 into IOURequestStepCategory.js What is the root cause of that problem?Cleaning of MoneyRequestConfirmPage What changes do you think we should make in orderThe component here will be deleted. Remove this line from ModalStackNavigation.js:
History page here has a few changes. Most of these are with the violations feature. We will take a look at the specific logic changes and add the changes to |
I would love to take this! |
ProposalPlease re-state the problem that we are trying to solve in this issue.Remove MoneyRequestConfirmPage.js and copy any changes since Nov 27 into IOURequestStepConfirmation.js What is the root cause of that problem?Remove deprecated component What changes do you think we should make in order to solve the problem?
App/src/libs/Navigation/linkingConfig.ts Line 429 in 278d04e
Lines 261 to 264 in a2f5bd5
Line 141 in a2f5bd5
App/src/libs/Navigation/types.ts Lines 188 to 191 in a2f5bd5
In here Lines 308 to 311 in a2f5bd5
We need to use the new :action param (instead of being hard-coded with "create") like we did here Lines 362 to 366 in a2f5bd5
What alternative solutions did you explore? (Optional) |
Job added to Upwork: https://www.upwork.com/jobs/~01d384157eb0d34e8a |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat ( |
Dibs |
I'd love to work on this issue. |
Upwork job price has been updated to $250 |
Looks like @DylanDylann has a more complete proposal. 🎀 👀 🎀 C+ reviewed |
Triggered auto assignment to @NikkiWines, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
Agreed! |
📣 @DylanDylann 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
waiting on PR |
I am working on PR |
Oh Hold. |
Still on Hold. |
@DylanDylann any updates? |
Waiting for this PR |
@NikkiWines, @parasharrajat, @adelekennedy, @DylanDylann Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@DylanDylann let's go, #34613 is merged. |
@adelekennedy Please remove the hold label |
@adelekennedy This issue is no more on Hold. In fact, the PR for this is merged. Please fix the title. |
thank you @parasharrajat! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.60-13 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-04-15. 🎊 For reference, here are some details about the assignees on this issue:
|
This comment was marked as outdated.
This comment was marked as outdated.
This is not a bug but a code refactor. Bug-zero checklist does not apply. cc: @adelekennedy |
No checklist - payment is due on 4/15 |
Payouts due:
|
Payment requested as per #34615 (comment) |
$250 approved for @parasharrajat |
This is a part of #29107. You can look at that issue for more context behind the cleanup process.
Problem
The app has two redundant components:
Old Component:
MoneyRequestConfirmPage
New Component
IOURequestStepConfirmation
Solution
Following the examples (example 1, example 2), the Old Component needs to be completely removed from the codebase
:action
param (instead of being hard-coded with"create"
)isEditing
to use the new action param from the routeUpwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: