-
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-02-14] [HOLD #24918][TS migration] Migrate 'IOU.js' lib to TypeScript #24926
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 Viktoryia from Callstack - expert contributor group - and I would like to work on this issue. |
Excited for this one – I think it will be particularly valuable. When can we expect a PR? |
@roryabraham For now, this one is blocked by ReportUtils and Policy.js migrations. I'll prioritize it as soon as it gets unblocked! |
HOLDing for #24918 |
Still on HOLD |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.37-7 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-02-14. 🎊 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:
|
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO. |
Please assign me here |
@aimane-chnaif offer out. |
Thanks. I know this is exception but just wanted to discuss amount based on the scale of PR, though TS migration. |
Triggered auto assignment to @mallenexpensify ( |
Reassigning for payment. Should be a quick one once we decide! |
@roryabraham 👀 please on the above. I'm brand new here as BZ so I don't want to jump in without much context. |
Taking this one back over - @roryabraham can you comment on the complexity of this one? |
@roryabraham mind chiming in? |
Yeah, I think it's fair to bump this one up to $750 due to the high volume of testing that had to happen. Saying that because it's probably 3x a "standard" TS migration issue |
Cool, all paid up. Closing! |
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. |
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: