-
Notifications
You must be signed in to change notification settings - Fork 41
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
Question: Email validation #13
Comments
note sure what you mean. the underlying react-netlify-identity library should handle it on every clientside render: https://github.com/sw-yx/react-netlify-identity/blob/8b083612664f6f0fa2be72cfd0dd5e9894916117/src/runRoutes.tsx#L53;L63 |
Nice! Thanks Shawn, I had started to code my own implementation using react+gotrue-js but should have just used the wrapper you've provided. |
would you mind if I made a PR on gotrue-js to add your wrapper to the docs? |
i thought its already there lol go for it, tag me in case i miss it |
Is there is a solution for handling email verification within Gatsby?
Reading the gotrue-js docs leads me to believe that the fragment identifier is slightly different to what you need to post to the backend for verification. Am I missing something?
The text was updated successfully, but these errors were encountered: