-
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-10-24] [$250] Migrate index.ios.js to function component #16137
Comments
|
I'd like to work on this issue |
I'd love to work on this. |
I am ready to work on this ticket. :) |
I can work on this issue. |
Can I work on this issue? |
I'd like to work on this. |
Dibs? |
Hello, I would like to work on this issue. |
Hi, |
dibs |
ProposalPlease re-state the problem that we are trying to solve in this issue.Migrate index.ios.js to function component What is the root cause of that problem?new feature What changes do you think we should make in order to solve the problem?we need to migrate the class component to the functional component
|
Dibs? |
Triggered auto assignment to @zanyrenney ( |
Triggered auto assignment to Design team member for new feature review - @shawnborton ( |
Thanks but there's already an assignee @mananjadhav |
@marcaaron Noted. |
PR is ready for review |
This issue has not been updated in over 15 days. @mananjadhav, @pasyukevich, @marcaaron, @MitchExpensify 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! |
Heads up @mananjadhav, there is a PR here waiting for your review |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.85-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-10-24. 🎊 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:
|
@MitchExpensify Can you please post the payment summary here? |
Payment summary: $250 - @mananjadhav (Eligible for Manual Requests) |
$250 approved for @mananjadhav based on comment above. |
@MitchExpensify I think it is safe to close this. It was a migration so no checklist needed. |
Thanks! |
Class Component Migration
Filenames
React.Component
Task
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: