-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[TS migration] Migrate 'ErrorUtilsTest.js' test to TypeScript #25274
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. |
Triggered auto assignment to @jliexpensify ( |
Hi, I'm Viktoryia from Callstack - expert contributor group - and I would like to work on this issue. |
Triggered auto assignment to @srikarparsi, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
@srikarparsi The PR is ready to merge! Do I need to get compensated for the test? It's pretty simple though. |
Hi @mollfpr - TS Migrations are $250, but I believe it's the same as any standard job. You should get paid out after deployment to prod. |
Thank you @jliexpensify! Could you assign me to the issue? Also, friendly bump @srikarparsi for the PR! |
Merged :) @jliexpensify I think we just need to pay @mollfpr $250 for reviewing the PR and we should be good to close since it was taken care of by Callstack. |
Great, here is a PAYMENT SUMMARY for JMills:
|
$250 approved for @mollfpr based on summary above. |
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
The text was updated successfully, but these errors were encountered: