You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[HOLD for payment 2023-08-01] [$250] Migrate BasePasswordPopover.js to function component #16188
changed the title [-][HOLD] Migrate BasePasswordPopover.js to function component[/-][+][HOLD][$250] Migrate BasePasswordPopover.js to function component[/+]on Apr 13, 2023
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.44-2 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-08-01. 🎊
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.
External issue reporter
Contributor that fixed the issue
Contributor+ that helped on the issue and/or PR
For reference, here are some details about the assignees on this issue:
@sobitneupanedoes not require payment (Eligable for Manual Requests)
Following on the above, I confirm that the above summary is correct and @sobitneupane is approved for payment via NewDot. @sobitneupane please create a request. Thanks!
Activity
[-][HOLD] Migrate BasePasswordPopover.js to function component[/-][+][HOLD][$250] Migrate BasePasswordPopover.js to function component[/+]dostongulmatov commentedon Jun 6, 2023
Proposal
Please re-state the problem that we are trying to solve in this issue.
Migrate BasePasswordPopover.js to function component
What is the root cause of that problem?
No problem, refactor the class component into functional component
What changes do you think we should make in order to solve the problem?
Update https://github.com/Expensify/App/blob/main/src/components/PasswordPopover/BasePasswordPopover.js
into functional component
dummy-1111 commentedon Jun 6, 2023
I'd love to work on this.
melvin-bot commentedon Jun 9, 2023
Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon Jun 13, 2023
Still overdue 6 days?! Let's take care of this!
melvin-bot commentedon Jun 15, 2023
Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!
melvin-bot commentedon Jun 19, 2023
12 days overdue now... This issue's end is nigh!
57 remaining items
melvin-bot commentedon Jul 25, 2023
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jul 25, 2023
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.44-2 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-08-01. 🎊
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:
JmillsExpensify commentedon Jul 26, 2023
@rayane-djouah Upwork job is here for when the regression period ends.
JmillsExpensify commentedon Aug 2, 2023
Payment summary:
JmillsExpensify commentedon Aug 2, 2023
Following on the above, I confirm that the above summary is correct and @sobitneupane is approved for payment via NewDot. @sobitneupane please create a request. Thanks!
techievivek commentedon Aug 7, 2023
Not overdue, waiting for the payment to complete.
sobitneupane commentedon Aug 9, 2023
Requested payment on newDot.
#16188 (comment)
JmillsExpensify commentedon Aug 10, 2023
We're all good on this one. Payment is approved via NewDot.