4
[Minor] auth.signInWithOtp improvement
Source: supabase/supabase#28373 · opened by @vyas-meet
This method generates a user on the fly (unless we prevent it by passing a boolean), or simply allows an existing user to sign in with a magic link.
We can also pass in metadata, but it is only relevant when a new user signs up. Otherwise, it goes into the void, not being used at all. This leads to inconsistencies and to deal with it, you need multiple DB calls like first check whether a user exists or not, and alike.
On a successful execution, it currently returns the following:
This is far from useful. It'd help if we at least get two parameters like:
These will help us process the user further if required, again considering the fact that the metadata is not handled if it's a login and not signup.
We can also pass in metadata, but it is only relevant when a new user signs up. Otherwise, it goes into the void, not being used at all. This leads to inconsistencies and to deal with it, you need multiple DB calls like first check whether a user exists or not, and alike.
On a successful execution, it currently returns the following:
This is far from useful. It'd help if we at least get two parameters like:
These will help us process the user further if required, again considering the fact that the metadata is not handled if it's a login and not signup.
No pledges yet. Be the first to back this.
Comments
Similar requests
I have an idea about the SignUp method
1 vote · 0 comments
IP of the entity that does auth, IP of entity that submits request
1 vote · 0 comments
Support generating access_token for phone users via Admin API
2 votes · 0 comments
Scoped Auth via non-unique emails on auth.users
4 votes · 0 comments
Cannot add "email" provider to an existing user
1 vote · 0 comments
No comments yet.