-
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-06-03] [TS migration] Migrate 'OptionsSelector' component to TypeScript #25125
Comments
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! |
@melvin-bot[bot], this Monthly task hasn't been acted upon in 6 weeks; closing. If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead. |
@melvin-bot[bot], this Monthly task hasn't been acted upon in 6 weeks; closing. If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead. |
Hello, I'm Tymoteusz Kałuzieński from Software Mansion, the expert agency, and I would like to work on this task. |
Triggered auto assignment to @Christinadobrzyn ( |
Hey @mountiny should there be an internal engineer assigned also? Should it be you or someone else? |
@cdOut from agency is working on this! |
we're working on this Melvin! |
@cdOut - Can you please make sure to address this TODO item in your PR: https://github.com/Expensify/App/pull/34168/files#diff-29ef0426ea09b0af3420c95911645adcd54c0d3d4c0d8c4fa5aa99dfe37a3646R604 ? |
Of course, I will include it in this TS migration. As a follow up, I am still waiting on this refactor to be finished to start working on migrating OptionsSelector. |
monitoring this - #31606 before @cdOut can continue with #25125 (comment) |
@Christinadobrzyn This should be paid only once since it's part of the same issue |
monitoring - #41077 |
1 similar comment
monitoring - #41077 |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
monitoring - #41077 |
PR is merged. Waiting for next deploy |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.75-1 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-06-03. 🎊 For reference, here are some details about the assignees on this issue: |
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:
|
No regression test needed. Neither a new feature nor a bug. |
Payouts due:
Upwork job is here. |
@Christinadobrzyn I think this should be still at $250 total based on the work done. |
Ah thanks for the heads up @s77rt - I'll adjust the payment back to $250 in Upwork when I pay this out. |
Held on payment. |
Payment Summary
BugZero Checklist (@Christinadobrzyn)
|
All paid out based on this summary #25125 (comment) Closing but let me know if you need anything! |
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
Issue Owner
Current Issue Owner: @ChristinadobrzynThe text was updated successfully, but these errors were encountered: