-
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-07-26] [$250] Migrate CategoryShortcutButton.js to function component #16143
Comments
ProposalPlease re-state the problem that we are trying to solve in this issue.-> Class Component Migration for CategoryShortcutButton Component What is the root cause of that problem?-> class components are more verbose and harder to reason about than functional components. What changes do you think we should make in order to solve the problem?-> Convert CategoryShortcutButton to functional component by removing extends Component , receiving props as input parameter and using arrow functionality syntax. What alternative solutions did you explore? (Optional) |
Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Huh... This is 4 days overdue. Who can take care of this? |
Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it! |
10 days overdue. I'm getting more depressed than Marvin. |
12 days overdue now... This issue's end is nigh! |
I'd like to work on this issue |
I'd love to work on this. |
I would like to work on this issue |
📣 @AGarciaNY! 📣
|
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
I can work on this issue. |
Is their any update on this? Can I work on this? |
@sakluger Can you assign a new CME as @puneetlath is OOO? |
feat[issue #16143]: Changed CategoryShortcutButton class component
I happened to see this, so went ahead and reviewed/merged. No need to re-assign @sakluger. |
Thanks @puneetlath! |
This issue is a bit different from what I'm used to. @marcaaron @puneetlath I assume that I need to hire and pay @AGarciaNY $250 through Upwork (@Santhosh-Sellavel requests payment through NewDot)? The linked PR was deployed to staging today, so estimated payment date is July 25. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.42-26 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-07-26. 🎊 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:
|
Yes, that sounds correct to me. |
1 similar comment
Yes, that sounds correct to me. |
Request $250 on ND |
Reviewed details for @Santhosh-Sellavel. This is accurate and approved for payment in NewDot. |
@sakluger could we get the payments handled on this one so that we can close it out? |
Sorry for the delay! @AGarciaNY I sent an offer to you through Upwork. Can you let me know once you've accepted? |
Hi @sakluger. I accepted it. |
Thanks! All paid up 🎉 |
Class Component Migration
Filenames
React.PureComponent
Task
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: