-
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 2024-11-11] [HOLD for payment 2024-10-30] [$250] Use new ValidateCodeActionModal component in as many places as possible #49270
Comments
Current assignees @hungvu193 and @getusha are eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to @jliexpensify ( |
Job added to Upwork: https://www.upwork.com/jobs/~021835679560526385104 |
Hmm no upwork jobs |
Current assignees @hungvu193 and @getusha are eligible for the External assigner, not assigning anyone new. |
We will handle this with the bois |
Any updates? @getusha 😄 . Let me know you if have any question. |
@hungvu193 found some edge cases, i'll try to finalize today |
@hungvu193 @getusha what is your ETA for the PR? |
I'll update today |
Looks like we added another page #49230, i'll try to include that as well |
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
This was a refactoring issue so not a bug to fix really, we do not need to create regression tests for this one and as such I dont think we need to fill in the checklist either |
Are we going to create a follow up PR to address the countdown timer? |
Payment Summary
|
Working on this one, hopefully i'll raise a PR today or tomorrow. |
As promised #51663 |
Payment Summary
BugZero Checklist (@jliexpensify)
|
@mountiny before I close this, are we also paying for the follow-up PR in this payment? Or will that be handled separately? If so, is that amount also $250? |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
We can pay it here, there was no new issue for that. I would say that we should have included that in the first pr so I would vote for partial reward for the second one so $375 total each for @hungvu193 and for @getusha |
This actually wasn't implemented in BaseValidateCodeForm before except the sign in page, but the amount sounds reasonable to me 👍 |
LGTM as well 😄 |
Great, thanks Vit - updated Payment Summary here. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.56-9 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 2024-11-11. 🎊 For reference, here are some details about the assignees on this issue:
|
@hungvu193 / @getusha @jliexpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
$375 approved for @hungvu193 |
$375 approved for @getusha |
We are requiring a validation of the primary login using magic code in more actions now, and as such, we are repeating the component that handles such login. We created the ValidateCodeActionModal component, but there are some places like Copilot and verifying secondary login that does not use this modal.
Let's use this new component and remove any other usages that could lead people to reintroduce the wrong usage/ component.
Discussed here https://expensify.slack.com/archives/C01GTK53T8Q/p1726493895290119?thread_ts=1726483475.882029&cid=C01GTK53T8Q
Issue Owner
Current Issue Owner: @Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @Issue Owner
Current Issue Owner: @jliexpensifyThe text was updated successfully, but these errors were encountered: