-
Notifications
You must be signed in to change notification settings - Fork 20
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
#676: Fix typos in coding-conventions asciidoc #677
base: main
Are you sure you want to change the base?
Conversation
Pull Request Test Coverage Report for Build 11176737615Details
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your corrections. I've added some suggestions but overall this looks nice.
@@ -146,10 +146,10 @@ Always use the logger to output messages and never use `System.out` or `System.e | |||
When catching exceptions always ensure the following: | |||
|
|||
* Never call `printStackTrace()` method on an exception | |||
* Either log or wrap and re-throw the entire catched exception. | |||
* Either log or wrap and re-throw the entire catch exception. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should still be catched
I think, as it is a catched exception.
Be aware that the cause(s) of an exception is very valuable information. | ||
If you loose such information by improper exception-handling you may be unable to properly analyse production problems what can cause severe issues. | ||
** If you wrap and re-throw an exception ensure that the catched exception is passed as cause to the newly created and thrown exception. | ||
** If you wrap and re-throw an exception ensure that the catch exception is passed as cause to the newly created and thrown exception. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should still be catched
I think, as it is a catched exception.
@@ -170,7 +170,7 @@ Exception in thread "main" java.lang.IllegalStateException: Something failed | |||
at com.devonfw.tools.ide.ExceptionHandling.main(ExceptionHandling.java:14) | |||
---- | |||
|
|||
As you can see we have no information and clue what the catched `Exception` was and what really went wrong in `doSomething()`. | |||
As you can see we have no information and clue what the catch `Exception` was and what really went wrong in `doSomething()`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should still be catched
I think, as it is a catched exception.
Co-authored-by: jan-vcapgemini <[email protected]>
Fixes: #676