-
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-11-30] [$250] Migrate AvatarWithImagePicker.js to function component #16119
Comments
This comment was marked as spam.
This comment was marked as spam.
Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Eep! 4 days overdue now. Issues have feelings too... |
8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it! |
10 days overdue. Is anyone even seeing these? Hello? |
This issue has not been updated in over 14 days. eroding to Weekly issue. |
I'd like to work on this issue |
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! |
I can work on this issue. |
Can I work on this issue? |
I'd like to work on this. |
dibs? |
Hey! I’m from Software Mansion, an expert agency, and I’d like to work on this issue. |
Dibs |
Dibs. Please give me 1 issue please |
I can work on this issue |
@eVoloshchak So from what I'm understanding, we need to change from a react class to a function component utilizing the function component paradigms for state, effects and lifecycle methods. While keeping the same functionality. Pretty straightforward 😀 I'll create a expensify account in the morning. |
📣 @joeysherman! 📣
|
@mountiny Could you give me a bit of context why the previous PR was closed and the issue got reassigned? Progress of the original PR is still blocked due to this (Form refactor issue), and until Form isn't refactored in |
Triggered auto assignment to @deetergp, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
BTW, discussed ith @blazejkustra 1:1, it was because it was stale. new approach showed we can create a new pr |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.2-3 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-11-30. 🎊 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:
|
This is ready for payment, @mountiny, could you post a payment summary please? |
@eVoloshchak getting $250 for review and testing. Since paid through newDot, I am going to close this issue now. @eVoloshchak can you note here when you request the reward in ND? |
Requested the payment, thx! |
$250 payment approved for @eVoloshchak based on comment above. |
Class Component Migration
Filenames
React.Component
componentDidMount
,componentWillUnmount
,componentDidUpdate
Task
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: