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
Requesting descriptive errors explaining what went wrong with a request, or even what likely went wrong #15270
Comments
I understand the sentiment, and having clear and actionable error messages (when it's possible for us to do so) is one of our design goals and something that's being slowly improved. However I can't approve the feature request because it doesn't have a clearly defined finite objective - it'd stay open forever. If you have specific error messages that need to be improved, consider opening feature requests for these instead. For instance, I assume what you mean about not using |
This issue has been automatically marked as stale because it has been open for 14 days without activity. It will be closed if no further activity occurs within the next 14 days. If this is still an issue, just leave a comment or remove the "stale" label. 🙂 |
@ephys could Sequelize just I hate errors coming from Sequelize so, so much because they almost never help me understand what went wrong. It can be such a time suck. I need a blanket solution to help me be more productive. |
I guess if nothing else I could just make some code monkeypatch the behavior I want onto Sequelize error classes. |
Okay, this is partly my goof in that I had some places logging |
Issue Creation Checklist
Feature Description
Describe the feature you'd like to see implemented
I want Sequelize to throw accurate errors describing what I did wrong with the tool to cause the error. The problem is usability. The requested feature would solve lots of hassles with using the product.
Describe why you would like this feature to be added to Sequelize
There are libraries that give accurate, informative responses to misuses of the product. Improving Sequelize's UX = sequelize will be used and recommended more = the hard work everyone puts into the project will get more benefit.
I'll give you what looks to me like a doable example that would immediately benefit your users: suppose the user doesn't authenticate with the db before trying to use a .create() method. Why can't the program raise an error: "you know you haven't authenticated yet, right?" You could add a flag within the package "hasSuccessfullyAuthenticated" and "if (!successfulAuthentication)" throw the error.
Is this feature dialect-specific?
Would you be willing to resolve this issue by submitting a Pull Request?
I would try to make these changes myself if my project backlog wasn't so bad.
Indicate your interest in the addition of this feature by adding the 👍 reaction. Comments such as "+1" will be removed.
The text was updated successfully, but these errors were encountered: