Remove Error from ThrowingExceptionsWithoutMessageOrCause because it's a common name #4046
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Error
is a common name for a class. If you have a class with that name and call it's constructor without any parameterThrowingExceptionsWithoutMessageOrCause
catches it as a false-positive. This is just a short term fix to avoid this type of false-positives but weThrowingExceptionsWithoutMessageOrCause
should use Type solving to avoid all the possible false-positives.Fix #4037