App: [$250] Remove MoneyRequestDatePage.js and copy any changes since Nov 27 into IOURequestStepDate.js
This is a part of https://github.com/Expensify/App/issues/29107. You can look at that issue for more context behind the cleanup process.
Problem
The app has two redundant components:
Old Component: MoneyRequestDatePage
New Component IOURequestStepDate
Solution
Following the examples (example 1, example 2), the Old Component needs to be completely removed from the codebase
- Look at the history of the Old Component
- If there are any changes since Nov 27, 2023 which have not been added to the New Component, copy those changes
- Replace all uses of the Old Component with the New Component
- Remove all traces of Old Component
- Be sure to update all routes and navigation to use the new
:actionparam (instead of being hard-coded with"create") - Update any logic like
isEditingto use the new action param from the route
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~0155d041c50cef598e
- Upwork Job ID: 1747632794805731328
- Last Price Increase: 2024-01-24
- Automatic offers:
- DylanDylann | Contributor | 28130672
- brunovjk | Contributor | 28132561
About this issue
- Original URL
- State: closed
- Created 5 months ago
- Comments: 39 (25 by maintainers)
All paid up
@brunovjk I think these changes also need to be included in your PR:
IOU.setMoneyRequestCreated()and all referencesIOU.setMoneyRequestCreated_temporaryForRefactor()toIOU.setMoneyRequestCreated()@muttmuure The PR was deployed to production 5 days ago. It seems the automation bot doesnβt work on this issue. Please help to move forward this one
As I know
MoneyRequestView.tsxis only used for REQUEST flow, and isnβt used in SPLIT_BILL flow. It is the reason why I hardcodedCONST.IOU.TYPE.REQUEST@brunovjk Please raise a PR soon
π£ @brunovjk π An offer has been automatically sent to your Upwork account for the Contributor role π Thanks for contributing to the Expensify app!
Offer link Upwork job Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review π§βπ» Keep in mind: Code of Conduct | Contributing π
@brunovjk Please wait to be assigned official before implementing PR
Thanks. Updated π
Discussed here about the fully expectation
@brunovjkβs proposal cover all cases. Letβs go with them
π π π C+ reviewed