useAuthActions() no signUp
Disclaimer: I'm green in the web-dev space (a Webflow developer that is fed up with No Code)
I'm curious as to why there is no "signUp" method. With BetterAuth and other implementations I notice that there is a separation between signIn and signUp.
It definitely simplifies the implementation of auth but are there further implications down the line? If anyone can enlighten me, I'm curious as to this design decision 🙂
3 Replies
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!
There's not really a distinction in OAuth between sign in and up, it just allows you to authorize a user with an external app and return it's user data, so that's why it's just called signIn
If you run signin and sign in with a new account it'll automatically be created
I see, that's kind of what I had assumed. If we were to compare Convex Auth to BetterAuth it really just was a design decision for the APIs?
- BetterAuth chose to be declarative about the SignUp api
- ConvexAuth chose to be imperative and have a generic signIn and "if this user doesn't exist, create it"
But either way, both solutions allow you to authorize a user with an external app (BetterAuth or ConvexAuth).
Appreciate the reply Danny - happy to see this community is helpful and engaging 🙂