-
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-10-23] [$250] Migrate OptionRow.js to function component #16181
Comments
|
I'd love to work on this. |
@marcaaron Do you think we should close this issue given the fact that we are going to break this component down into multiple components and then gradually remove it? |
I'd say if we are doing something like that then this can just remain on HOLD until the component no longer exists and we can close it then. |
This comment was marked as spam.
This comment was marked as spam.
Job added to Upwork: https://www.upwork.com/jobs/~01569e90e356901c93 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @narefyev91 ( |
This one still exists so 🚀 |
📣 @s-alves10 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
@s-alves10 Gonna assign you here since you expressed interest in the past. Hopefully you are still interested? Thanks! |
ProposalPlease re-state the problem that we are trying to solve in this issue.this component is class based What is the root cause of that problem?What changes do you think we should make in order to solve the problem?we should migrate to functional components. What alternative solutions did you explore? (Optional) |
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 🚀 |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.83-11 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-10-20. 🎊 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:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.83-11 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-10-20. 🎊 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:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.84-10 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-10-23. 🎊 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:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.84-10 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-10-23. 🎊 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:
|
@narefyev91, @marcaaron, @s-alves10 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Oh hmm someone needs to do the payment before we close. Adding a BZ. |
Triggered auto assignment to @conorpendergrast ( |
This comment was marked as duplicate.
This comment was marked as duplicate.
@marcaaron To confirm, I'm paying @s-alves10 $250 via this offer? |
Yep |
Well great. That has been done! Payouts due: Issue Reporter: N/A
Contributor+: @narefyev91 - contractor Eligible for 50% #urgency bonus? No Upwork job is here. |
Class Component Migration
Filenames
React.Component
componentDidUpdate
,shouldComponentUpdate
Task
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: