-
Notifications
You must be signed in to change notification settings - Fork 486
Add error-prone.picnic.tech
featuring StaticImport
#2664
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
base: main
Are you sure you want to change the base?
Conversation
6d13e79
to
da00d3a
Compare
gradle/error-prone.gradle
Outdated
'AsyncCallableReturnsNull,' + | ||
'AsyncFunctionReturnsNull,' + | ||
'AutoValueBuilderDefaultsInConstructor,' + | ||
'AutoValueConstructorOrderChecker,' + |
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.
might not need all but it should not hurt as its only local and opt-in.
da00d3a
to
75726d1
Compare
error-prone.picnic.tech
error-prone.picnic.tech
featuring StaticImport
75726d1
to
7433670
Compare
|
7433670
to
d511b46
Compare
d511b46
to
a7f79d2
Compare
This seems like a good addition to Rewrite, as in some aspects it is superior and has its unique benefits—like every tool has. Of course, they cover the same topic, like It's behaving just like Rewrite—failing the build and suggesting changes. The opt-in is quite unique and will not be communicated like in Rewrite, but the changes should be small, like the changesets. Do you like to see this going on? @nedtwigg Thanks. |
on corruption:
relates to:
error-prone.picnic.tech
featuringRedundantStringConversion
junit-team/junit-framework#5006RecipeNullabilityBestPractices
#2663