Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Exposing ResponseError data type #34

Open
onepunchtech opened this issue Dec 20, 2021 · 0 comments
Open

Exposing ResponseError data type #34

onepunchtech opened this issue Dec 20, 2021 · 0 comments

Comments

@onepunchtech
Copy link

I'm wondering if it would be a good idea to expose the ResponseError constructors to allow users to make smarter decisions about errors.

For example the error type "Neo.ClientError.Schema.ConstraintValidationFailed" can sometimes be used to determine if there should be a user input error vs an internal server error. Similar to 400 vs 500 http error codes.

Or am I missing some other method to be able to distinguish between the error types in the KnownResponseFailure?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@onepunchtech