Adding error codes to ApiError

[samirergaibi]

Feature request

Is your feature request related to a problem? Please describe.

I am building a website with supabase and the errors that is returned from supabase.auth only contains a general error code 400 and a message in english. This makes the different errors hard to distinguish from eachother.

Example:
User tries to create an account but the user is already registered so the error returned from supabase.auth.signUp will be

{ 
  message: "User already registered",
  status: 400
}

Describe the solution you'd like

If the error included a specific error code mapped to particular error then providing a custom message would be easy.

Example:

{ 
  message: "User already registered",
  status: 400,
  errorCode: 1,
}

It would also be really awesome if the error codes was included in the documentation.

Describe alternatives you've considered

I've considered checking the string value returned in the error but if that would change in the future that would in turn break the application.

[joeyTedeschi]

+1 for this change, as at this time distinguishing between errors (and translating them to different languages), is completely contingent on parsing the message being returned (and if that message one day got changed, it would break whatever logic we've had to build on top of it)

[salazarr-js]

I realize that when a user signs up using an already in use email don't get any error messages, auth.signUp() just returns the user. i think in this case i wanna cath the error and tell the user that email is in use

a User already registered error message would be awesome

[Andrewjeska]

I want to alert the user if they need to check their email for the invite link, so error code would be help on signIn here would really help

[aiji42]

I strongly support this request!
Error codes would facilitate the creation of dictionary data for translation and help with multilingualization.

I am developing an application for Japanese and currently there is no list of error messages, so I am having a hard time creating dictionary data.

[florianwalther-private]

+1 on this. How am I supposed to provide the user additional steps if their login attempt errors because their email hasn't been verified yet, but they can't find the verification code anymore?

[silentworks]

Related to supabase/supabase#12739

[nickreese]

Interested in this.

[raheemja]

Over a year later and this has not been addressed. I thought features like this were standard practice.

[renansoares]

no news on this? how people are handling authentication errors and internalization?

[sharifbubuka]

Thought this was industry standard and not something to implement upon request. Any developments on this?

[otyang]

This just made ditch supabase Auth for something else.

Its standard practise to return proper errors.

But till now over a year nothing has been done. There is no proper CURL documentation for us to implement the rest Auth into a SDK ourselves.

Even on the little examples, errors are not treated well. this is a no no for me,shows an unserious company in this aspect