Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Error message concept #2435
@markus2330, I rewrote the concept. Please give your final review so I can finally start.
I reworked the concept as you desired @markus2330 and also investigated other projects. I liked the SQLSTATES and incorporated it into the concept. The categories as of now did not change because I did not see the need for it when going through other error categories.
The categories are fine for me now, I think you can implement this in the error specification.
For the API there are still discussions (SOLUTION) and extensions (high-level API?) needed.
I think you should split this to several decision files. In this PR please only add the error specification so that we can finally merge this.
The current error codes of the high-level API could simply integrated into the new concept. Either as their own category or otherwise marked with some attribute. The
This would also be good test for whether the concepts is usable, if a different error reporting framework (other than an
Mar 27, 2019
Mar 28, 2019
5 of 6 checks passed
After categorizing some errors I would kind of tend to have an own category because all errors from other languages could also be included there (python, java, etc.)
Maybe we could call is