ETA for smarter merging of accounts
Is there any ETA for the 'smarter merging of accounts'?
I made an app with email & social auth that relies on users inviting other users to their workspaces.
I'm a bit stuck as invited users can only login using their email and password, which is a bit confusing as I'm also offering social auth.
Ofcourse their social auth doesn't work as they've registered using email/pass. π
Any tips on workarounds meanwhile?
5 Replies
hmm its hard to know for sure what you mean without seeing some examples / code.
Do you want to see a live example? I can invite you to my workspace, send me your email π
Or I can give you access to my Github repo?
paste a code snippet here or send a link to the lines in your repo responsible for this feature
I understand what you mean, we talk about this in the docs here: https://wasp-lang.dev/docs/auth/email
I can't provide a definitive ETA but what I can tell you is that we plan on working on making Wasp more stable and usable in the next quarter. We are looking for missing pieces like "smarter merging of social + email accs" which we still need to polish.
A workaround within Wasp is not possible ATM ... you could try having two fields for the email or similar. Or even go as far as implementing the oAuth by yourself π’
Email | Wasp
Wasp supports e-mail authentication out of the box, along with email verification and "forgot your password?" flows. It provides you with the server-side implementation and email templates for all of these flows.
hmm yeah I agree that is a bit tricky! for now probably the best thing to do is to offer only email or only social as the auth method.
btw I'd love to see what you've built if possible! π my email is [email protected]