-
Notifications
You must be signed in to change notification settings - Fork 108
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
Email verification screen (6 digit code screen) #233
Comments
Can I try to create this for SWE? |
Yes! Good luck and if you any questions @alexwala in discord (OSC DISCORD) and or come in person to OSC's casual codings to talk to me :) |
@jqiu0601 updates? |
Should I make a pull request showing my current progress even if I still haven't finished? I'm currently having trouble trying to import a submit button that I repurposed from an existing log in button |
I'll definitely have to ask about this in CC tomorrow |
Update? |
just finished two exams on monday and today, finally free to code
…________________________________
From: Dylan Coben ***@***.***>
Sent: Tuesday, October 22, 2024 5:07 PM
To: ufosc/OSC-Proximity-Chat-App ***@***.***>
Cc: Qiu, Jake ***@***.***>; Mention ***@***.***>
Subject: Re: [ufosc/OSC-Proximity-Chat-App] Email verification screen (6 digit code screen) (Issue #233)
[External Email]
Update?
—
Reply to this email directly, view it on GitHub<#233 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A34CBAYWRGYMPGEIIKUYJS3Z425AFAVCNFSM6AAAAABNNHTMKSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZQGI4DONZUGE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
In the figma (linked in the pinned in the discord in #echologators) there should be a design for a 6 digit email authentication service. Please make that screen and its functionality but without actually making any requests. The user should be able to enter any 6 digit code and pass through. However, you must also add possibility of extending to actual authentication (such as hooks/handles for rejecting the code) etc etc.
The text was updated successfully, but these errors were encountered: