Closed Beamanator closed 1 year ago
Triggered auto assignment to @shawnborton (Design
), see these Stack Overflow questions for more details.
If we use our existing input style and break it out into 6 inputs like your example above, we'd get something like this:
It would be nice to rethink this flow a bit in the future and add in more branding elements and animations though:
I'll take over this one.
I love the above design. Do we want to also use it to 2fa input field?
Oh that would make sense as well, yeah!
I'm HYPED for this! Thanks for pushing this forward!
Yess, this'll look so great!! 🚀
I'll work on this late this week.
I'll offload this to Callstack since it is only front-end work.
Hi, I'm Ana from Callstack, I'll pick this up!
Woo! Can't wait to get this one in product. It looks soooooo good.
Currently the magic code input is just a text input with a number pad keyboard. It would be interesting to follow the same pattern set by other apps, and have a specific input type for magic codes.
The current solution looks like a typical text input. This does not make it clear what is the structure of the magic code and it allows for pasting other content that is not only a 6 digit code.
Create a MagicCodeInput that:
onChangeText
, onSubmitEditing
and prop value
TextInput
componentsNone.
Looks good to me 👍
Create a MagicCodeInput that:
- contains 6 text inputs (using numeric keyboard)
- each input should only allow for one number
- receives a number as a prop and only allows numeric input
- handles the focus logic
- auto-focus on the first input
- focus on the next input when the previous is complete
- once all inputs are complete, it submits
- when pressing backspace, it should delete and focus on the previous input
- if an input with a value is focused, when adding another value it should replace it
- handles paste events to fill the input correctly
- show error message
- use the same callbacks
onChangeText
,onSubmitEditing
and propvalue
@shawnborton Could you also have a look at the above?
Looks pretty good to me!
Thank you!
@BeeMargarida , you're good to go with the implementation!
Thank you, on it!
Almost ready, just working on some optimization problems with the focusing logic in Android phones
Update: Just reviewing/testing the code, should be ready today or monday
The PR is ready for review
@shawnborton, @cristipaval, @BeeMargarida Whoops! This issue is 2 days overdue. Let's get this updated quick!
PR is in review Melvin
@shawnborton, @cristipaval, @BeeMargarida Eep! 4 days overdue now. Issues have feelings too...
@aimane-chnaif has to review the PR.
Sorry, reviewing PR today
@shawnborton, @cristipaval, @BeeMargarida, @aimane-chnaif Whoops! This issue is 2 days overdue. Let's get this updated quick!
@shawnborton, @cristipaval, @BeeMargarida, @aimane-chnaif 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
Waiting for another review on the PR
@shawnborton, @cristipaval, @BeeMargarida, @aimane-chnaif Whoops! This issue is 2 days overdue. Let's get this updated quick!
@shawnborton, @cristipaval, @BeeMargarida, @aimane-chnaif Eep! 4 days overdue now. Issues have feelings too...
Waiting for a review on the PR
@shawnborton, @cristipaval, @BeeMargarida, @aimane-chnaif 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!
@shawnborton, @cristipaval, @BeeMargarida, @aimane-chnaif 10 days overdue. I'm getting more depressed than Marvin.
This will get into production soon, Melv.
Reviewing
label has been removed, please complete the "BugZero Checklist".
The solution for this issue has been :rocket: deployed to production :rocket: in version 1.3.12-0 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2023-05-16. :confetti_ball:
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:
Not overdue
Can someone add New Feature
label to assign BZ member?
Can do!
Triggered auto assignment to @joekaufmanexpensify (NewFeature
), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details.
Thanks @shawnborton
Okay, since @BeeMargarida is with Callstack, their payment will be handled separately. So we just need to pay @aimane-chnaif $1,000 for their C+ review.
Job added to Upwork: https://www.upwork.com/jobs/~018a8f57a7a625d18f
Current assignee @joekaufmanexpensify is eligible for the External assigner, not assigning anyone new.
Current assignee @aimane-chnaif is eligible for the External assigner, not assigning anyone new.
Current assignee @cristipaval is eligible for the External assigner, not assigning anyone new.
@aimane-chnaif offer sent for $1000!
@aimane-chnaif $1,000 sent and contract ended!
Upwork job closed.
This was a new feature, so BZ checklist is not necessary. Feature is implemented, and all payment issued. Closing as this is all set, thanks everyone!
cc @twisterdotcom as this was your idea
cc @johnmlee101 @NikkiWines as y'all are the passwordless pros!
Problem
The currently magic code input is very boring, lets spice it up!
Solution
Implement a cool magic code entry with individual fields per digit.
Note: We should plan out exactly how we want this to work before implementing, example:
We might even want to implement something like "Resend code in" so users can only try to resend magic codes once per... minute?
Here's an idea we can start with, from another website:
Upwork Automation - Do Not Edit