-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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-21] [$250] Migrate ReportTypingIndicator.js to function component #16269
Comments
@danieldoglas taking this issue off HOLD as per this Slack post IMPORTANT: If anything unexpected pops up during the refactor/review:
|
|
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. |
I'll actually unassign this one from me and leave it open for when we reach external people. |
Job added to Upwork: https://www.upwork.com/jobs/~017bb70fdccbb440b5 |
Triggered auto assignment to @miljakljajic ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @eVoloshchak ( |
Triggered auto assignment to @hayata-suenaga ( |
I would like to take this |
I'd like to work on this issue |
I would like to work on it. |
Title: Migrate ReportTypingIndicator.js to function component Problem: ReportTypingIndicator.js was written as a class component and hence not in accordance with latest react conventions. Suggested Solution: Rewrite ReportTypingIndicator.js as a functional component so that we are up to date with latest react conventions and also to be able to use hooks. |
I would like to take this |
📣 @achmadk! 📣
|
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
@eVoloshchak I think the first one who posts a comment is picked for migration issues |
@hayata-suenaga, agree, for the issues where the investigation isn't needed and the scope of work is clearly defined - whoever posts the comment first is assigned to the issue seems like the logical approach, so let's proceed with @jayeshmangwani's proposal |
📣 @jayeshmangwani You have been assigned to this job by @hayata-suenaga! |
Thanks for the wise consideration, @eVoloshchak @hayata-suenaga. Maybe I can contribute to the Expensify app in another issue. @jayeshmangwani, please do your best! |
PR is ready for review |
@eVoloshchak, @miljakljajic, @jayeshmangwani, @hayata-suenaga Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Not overdue, this was deployed to staging 2 days ago |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.27-7 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-21. 🎊 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:
|
Just to confirm - will @eVoloshchak and @jayeshmangwani be owed 250 USD each for this issue? I will send out the offers today so we're ready to pay on the 21st. |
@miljakljajic I found a slack comment by Marc on contributor compensation being $250 |
I'll issue payment today! |
contracts extended @jayeshmangwani and @eVoloshchak |
Paid, contracts ended. |
Class Component Migration
Filenames
React.Component
componentDidUpdate
Task
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: