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
For the error types exposed here we should have a class with constants or an enum so we don't have to manually put the string in the code.
Let say I want to display some error message specifically to the user depending on the type, so instead of doing this:
AppWriteException exception; if (exception.type == 'user_already_exists') { ... }
I could use the constant instead
AppWriteException exception; if (exception.type == ErrorType.userAlreadyExists) { ... }
The text was updated successfully, but these errors were encountered:
Hi - thank you for opening this This really does sound helpful, keeping it open for gathering feedback.
Sorry, something went wrong.
This is a really good idea. We'll be working on implementing this across all of our SDKs. Thank you for the suggestion @santigarcor!
Is there anything I can do to help?
Not sure yet, but if there will be we'll keep updates in this issue 👍
joeyouss
No branches or pull requests
🔖 Feature description
For the error types exposed here we should have a class with constants or an enum so we don't have to manually put the string in the code.
🎤 Pitch
Let say I want to display some error message specifically to the user depending on the type, so instead of doing this:
I could use the constant instead
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: