We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
/api/login
/api/signup
They should return HTTP status code 400 if the server receives a bad request, such as the email and password not being strings.
See here.
The text was updated successfully, but these errors were encountered:
400 will route the client to /api/signup or /api/login so 404. Maybe a 302 with a URI error like what currently happens on a supabase error?
Sorry, something went wrong.
I realise that the Supabase's auth functions take care of these bad request scenarios by removing assertions. PR submitted.
No branches or pull requests
They should return HTTP status code 400 if the server receives a bad request, such as the email and password not being strings.
See here.
The text was updated successfully, but these errors were encountered: