Is the isEmailAutoVerified boolean accessible/usable/exposed?
Seen here: https://github.com/wasp-lang/wasp/blob/246ae9c7824002d92a17dcf2f027e6f86d0c8cea/waspc/data/Generator/templates/server/src/auth/providers/email/signup.ts#L35C2-L35C34
I saw it used for the SKIP_EMAIL_VERIFICATION_IN_DEV flag but not sure if it's exposed for main.wasp use. Thanks!
4 Replies
Hi @NemusAI. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the provided knowledge sources, the
isEmailAutoVerified boolean is not directly exposed for use in the main.wasp file. However, you can control the email verification process in development mode by using the SKIP_EMAIL_VERIFICATION_IN_DEV environment variable.
You can set this variable to true in your .env.server file to skip the email verification step. This can be useful when you are developing your app and don't want to go through the email verification flow every time you sign up or when you are writing automated tests for your app.
Here is how you can set it:
By default, Wasp requires the email to be verified before allowing the user to log in. This is done by sending a verification email to the user's email address and requiring the user to click on a link in the email to verify their email address.
For more details, you can refer to the Wasp documentation on Email Verification Flow (https://wasp-lang.dev/docs/auth/email#email-verification-flow).
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @NemusAI, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?Yeah you can't access that one I am afraid, it is an implementation details.
Let me ask the expert though: @miho , is there any way to "hack" Wasp right now to skip email verification in production? But I guess we also want to not show that message "go check your email"
My "solution" was quite janky but for future - I enabled username auth and then forced a change to the label for
username to change it to email
Not proud of it but it works 😅Ha that is one way to go about it for now! Stay tuned for updates, we will certainly provide better support in the future.