-
Notifications
You must be signed in to change notification settings - Fork 134
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
Enable PreferCollectionConstructors by default #1386
Conversation
Generate changelog in
|
@@ -57,7 +57,7 @@ | |||
name = "CatchSpecificity", | |||
link = "https://github.com/palantir/gradle-baseline#baseline-error-prone-checks", | |||
linkType = BugPattern.LinkType.CUSTOM, | |||
severity = BugPattern.SeverityLevel.SUGGESTION, | |||
severity = BugPattern.SeverityLevel.WARNING, |
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.
I recall there being a reason we had this one set only to suggeation. @carterkozak do you remember why? or is my memory getting corrupted?
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.
Looks like we just wanted to validate that it did the right thing and then planned to increase the severity.
#941 (comment)
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.
I think we wanted to roll out the refactors for a while before adding the requirement to avoid friction.
Adding do not merge, while waiting for a response to my question. Otherwise LGTM 👍 . Thanks @pkoenig10 |
a4dbf2d
to
840ad40
Compare
840ad40
to
01d9371
Compare
Released 3.23.0 |
This excavator has been out for a while so making this a
WARNING
should not result in too much additional code churn.Also update severity on some checks I missed in #1380.