Skip to content
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

Merged
merged 2 commits into from
Jun 3, 2020

Conversation

pkoenig10
Copy link
Member

@pkoenig10 pkoenig10 commented Jun 3, 2020

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.

@changelog-app
Copy link

changelog-app bot commented Jun 3, 2020

Generate changelog in changelog/@unreleased

Type

  • Feature
  • Improvement
  • Fix
  • Break
  • Deprecation
  • Manual task
  • Migration

Description

The PreferCollectionConstructors error-prone check is now enabled by default.

Check the box to generate changelog(s)

  • Generate changelog entry

@policy-bot policy-bot bot requested a review from iamdanfox June 3, 2020 17:47
@@ -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,
Copy link
Contributor

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?

Copy link
Member Author

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)

Copy link
Contributor

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.

@ferozco
Copy link
Contributor

ferozco commented Jun 3, 2020

Adding do not merge, while waiting for a response to my question. Otherwise LGTM 👍 . Thanks @pkoenig10

@pkoenig10 pkoenig10 force-pushed the pkoenig/collectionConstructors branch from a4dbf2d to 840ad40 Compare June 3, 2020 19:30
@pkoenig10 pkoenig10 force-pushed the pkoenig/collectionConstructors branch from 840ad40 to 01d9371 Compare June 3, 2020 19:32
@bulldozer-bot bulldozer-bot bot merged commit 3901215 into develop Jun 3, 2020
@bulldozer-bot bulldozer-bot bot deleted the pkoenig/collectionConstructors branch June 3, 2020 20:11
@svc-autorelease
Copy link
Collaborator

Released 3.23.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants