Contribute to help us improve!
Are there edge cases or problems that we didn't consider? Is there a technical pitfall that we should add? Did we miss a comma in a sentence?
If you have any input for us, we would love to hear from you and appreciate every contribution. Our goal is to learn from projects for projects such that nobody has to reinvent the wheel.
Let's collect our experiences together to make room to explore the novel!
To contribute click on Contribute to this page on the toolbar.
Use a common base class
All business exceptions should inherit a common abstract base class so they can be distinguished from technical exceptions.
Should be inheriting
Should store the cause
Should contain a reason enum. The enum is project individual and contains values like
IncorrectInput. This enum can later be used to decide how to inform the user about the problem e.g. via HTTP status codes when building REST apis.