-
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 2023-06-19] [$250] Migrate ReportFooter.js to function component #16268
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. |
Lower priority right now but I will try to get to this soon |
Heads up, I'm taking this issue off |
I can work on this if goes to external |
Job added to Upwork: https://www.upwork.com/jobs/~01587290f1883b1269 |
Triggered auto assignment to @MitchExpensify ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @s77rt ( |
Current assignee @mountiny is eligible for the External assigner, not assigning anyone new. |
@dhairyasenjaliya are you working on anay other refactor now? following this guideline https://expensify.slack.com/archives/C01GTK53T8Q/p1685729601728839?thread_ts=1685727880.152119&cid=C01GTK53T8Q |
I would like to take this refactoring |
@mountiny currently not working on any refactoring task |
I would like to take this. |
@dhairyasenjaliya since you were first on this issue after the announcement in Slack, I am going to assing you |
📣 @dhairyasenjaliya You have been assigned to this job by @mountiny! |
Thanks everyone, be on a look out for other migration issues, assigning @dhairyasenjaliya as they were the first one to raise hands after the announcement |
alright PR coming up soon thnx @mountiny |
ProposalPlease re-state the problem that we are trying to solve in this issue.Refactor the component src/pages/home/report/ReportFooter.js to a function component What is the root cause of that problem?Class components are deprecated. We need to upgrade the component to the function component by following the guidelines: https://react.dev/reference/react/Component#alternatives. What changes do you think we should make in order to solve the problem?
What alternative solutions did you explore? (Optional)NA |
@petromoldovan thanks for the proposal, since these issues are quite straightforwards, we are going based on the first come firse serve basis and each developer only has one assigned at the time, see this update in slack for more info https://expensify.slack.com/archives/C01GTK53T8Q/p1685727880152119 |
Is it open ? |
@Vishrut19 This issue does not have |
Pr Merged 🎉 |
Awesome 👌 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.26-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 2023-06-19. 🎊 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.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
Payment reminder set in my cal 👍 |
Invites sent for payment @s77rt @dhairyasenjaliya 👍 |
Paid with bonuses! |
I don't think bonus applies for migration. I have refunded the bonus. |
Yeah agree will refund too within an hour |
Refunded bonus :) @MitchExpensify |
Ah, thanks for the catch team! I appreciated the speed of assignment to merge all the same 😆 |
Class Component Migration
Filenames
React.Component
Task
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: