You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an exception is caught and a new exception is generated, the old exception should be chained into the new one (unless there is a very good reason not to do it and this should be document in a code comment).
Also, when an exception is handled and thrown up/chained into a new exception, it should normally be unnecessary to log it because it should be expected that the exception is handled again at a higher level leading to the problem likely being logged twice.
The text was updated successfully, but these errors were encountered:
When an exception is caught and a new exception is generated, the old exception should be chained into the new one (unless there is a very good reason not to do it and this should be document in a code comment).
Also, when an exception is handled and thrown up/chained into a new exception, it should normally be unnecessary to log it because it should be expected that the exception is handled again at a higher level leading to the problem likely being logged twice.
The text was updated successfully, but these errors were encountered: