[HOLD for payment 2024-06-11] [TS migration] Migrate '[Remaining]' model to TypeScript

[melvin-bot]

TypeScript migration

Make sure you read through our TypeScript's style guide, cheatsheet and PropTypes conversion table before you start working on this migration issue.

Files

Path	Dependencies
src/pages/reportMetadataPropTypes.js	1
src/pages/nextStepPropTypes.js	1
src/pages/settings/Wallet/assignedCardPropTypes.js	2
src/components/transactionPropTypes.js	3
src/components/tagPropTypes.js	1
src/components/optionPropTypes.js	4
src/components/categoryPropTypes.js	1

Issue Owner

Current Issue Owner: @johncschuster

[melvin-bot]

This issue has not been updated in over 15 days. 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!

[blazejkustra]

Hey! I’m Błażej Kustra from Software Mansion, an expert agency, and I’d like to work on this issue!

[web-cloudy]

Hi,
I am Pavlo.
I’d like to work on this issue

[melvin-bot]

Triggered auto assignment to @johncschuster (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details. Please add this Feature request to a GH project, as outlined in the SO.

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.78-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [No QA][TS migration] Remove all remaining prop-types from the project #42249

If no regressions arise, payment will be issued on 2024-06-11. 🎊

[melvin-bot]

BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
• [@johncschuster] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.

[johncschuster]

@hayata-suenaga I see you were involved in the PR review. I don't believe we'll need a regression test, but I'm not certain. Am I correct in my thinking?

[hayata-suenaga]

this is a TypeScript migration issue so no regression is needed 😄

One of the expert agency engineer worked on this issue and there was no C+ involved in the PR review so there is no payment needed for this issue.

I believe we can close this issue 👍 closing this now. thank you everyone for working on this 😄