-
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-01-17] [TS migration] Migrate 'FloatingActionButton.js' component to TypeScript #25055
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! |
Hi, I'm Julian from Callstack - expert contributor group - and I would like to take a look at this issue. |
@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. |
This issue is blocked by #16150 |
This issue is no longer blocked! |
The PR is ready for review! |
Triggered auto assignment to @roryabraham, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
Triggered auto assignment to @sophiepintoraetz ( |
@sophiepintoraetz hi 👋🏼 the PR was just merged, and the only payment due here is $250 to @eVoloshchak for the C+ review of a TS migration PR (pending deploy to prod and regression period) |
offer sent |
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. |
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. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.23-4 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-01-17. 🎊 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:
|
@sophiepintoraetz, could you post a payment summary here please? |
Thanks for the transparency @eVoloshchak! Confirming that the payment should be $62.5 |
@sophiepintoraetz, any updates on the above? |
Contributor+: @eVoloshchak due $62.50 via NewDot |
$62.50 approved for @eVoloshchak |
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: @sophiepintoraetzThe text was updated successfully, but these errors were encountered: