-
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 2023-08-08] [$250] Migrate BasePaymentsPage.js to function component #16287
Comments
|
Heads up! The pricing for this issue has been adjusted based on the scope of the work and the fact that no complex bug investigations or proposal are required. |
Heads up, I'm taking this issue off |
I would like to take this issue |
@aldo-expensify Whoops! This issue is 2 days overdue. Let's get this updated quick! |
This comment was marked as off-topic.
This comment was marked as off-topic.
Oops, the PR was for another component, ignore message above. I'll try to get to this tomorrow or early next week. |
@aldo-expensify Whoops! This issue is 2 days overdue. Let's get this updated quick! |
I'll get to this later during the week. |
Hello |
@aldo-expensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Started to work on this yesterday. |
Now awaiting internal engineering review! |
Based on my calculations, the pull request did not get merged within 3 working days of assignment. Please, check out my computations here:
On to the next one 🚀 |
@stephanieelliott When payment is due @Natnael-Guchima is eligible for a reporting bonus for this regression. It's being handled in this PR Thanks! |
Based on my calculations, the pull request did not get merged within 3 working days of assignment. Please, check out my computations here:
On to the next one 🚀 |
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.3.48-5 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 2023-08-08. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
Summarizing payment on this issue:
Upwork job is here, no bonus since this was a small migration |
Accepted the offer. Thanks @stephanieelliott |
Hi, @stephanieelliott |
Requested on ND |
@stephanieelliott could you please take a look at @multijump's issue. We can close it the issue then |
Hey @multijump try this link: https://www.upwork.com/jobs/~013ebab8a106d7ab8f Otherwise, if you let me know your name on Upwork I can invite you to the job! @Natnael-Guchima has been paid! |
Hi, @stephanieelliott |
Review the details for @Santhosh-Sellavel. Approved for payment in NewDot based on the summary from BZ above. |
All paid! |
Class Component Migration
Filenames
React.Component
componentDidMount
,componentDidUpdate
Task
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: