-
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
[HOLD for payment 2024-02-15] [$250] [TS migration] Migrate 'SettlementButton.js' component to TypeScript #25100
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. |
Job added to Upwork: https://www.upwork.com/jobs/~018a41880e78febd6d |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @narefyev91 ( |
Upwork job price has been updated to $250 |
i would love to take it |
I would like to work on this |
ProposalPlease re-state the problem that we are trying to solve in this issue.[TS migration] Migrate 'SettlementButton.js' component to TypeScript What is the root cause of that problem?Not problem (Technical ticket ) What changes do you think we should make in order to solve the problem?We need to update this file using best practices using TS guide https://github.com/Expensify/App/blob/main/contributingGuides/TS_STYLE.md What alternative solutions did you explore? (Optional)NA |
I would like to work on this issue |
@ZhenjaHorbach is the first to #25100 (comment) with no other TS issue assigned. 🎀 👀 🎀 C+ reviewed. |
📣 @hoangzinh 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
Triggered auto assignment to @twisterdotcom ( |
Yep thanks |
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. |
This issue has not been updated in over 15 days. @AndrewGable, @twisterdotcom, @hoangzinh, @ZhenjaHorbach 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! |
The PR was merged two hours ago: #33866 I'll need to pay out @hoangzinh when it's deployed. Hopefully the title changes. |
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.38-6 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-15. 🎊 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 need for regression tests, this is a TS migration. |
Payment summary:
|
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
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: