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.

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

Re-think how we organize error messages #557

Open
gajus opened this issue Mar 28, 2024 · 0 comments
Open

Re-think how we organize error messages #557

gajus opened this issue Mar 28, 2024 · 0 comments

Comments

@gajus
Copy link
Owner

gajus commented Mar 28, 2024

Now that we've introduced driver abstraction, is clear that:

  • Slonik must be responsible for standardizing error classes
  • Driver must be responsible for mapping errors

However, as the number of errors has proliferated, there is a need to better organize errors. At the very least, we should make it clear which errors are originating from the driver VS from within Slonik client.

We should also add abstraction for common error types, e.g. I noticed P0001 is missing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant