-
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
Add an ErrorProne check for raw types #1197
Conversation
Generate changelog in
|
I'm supportive of this. Have we run it on a large repo to make sure that it doesn't cause any unexpected breaks? Also the changelog message should be a one-line sentence explaining what you're adding, just "Add an ErrorProne check for raw types" should be enough |
baseline-error-prone/src/main/java/com/palantir/baseline/errorprone/RawTypes.java
Outdated
Show resolved
Hide resolved
...eline-java/src/main/groovy/com/palantir/baseline/extensions/BaselineErrorProneExtension.java
Outdated
Show resolved
Hide resolved
baseline-error-prone/src/main/java/com/palantir/baseline/errorprone/RawTypes.java
Outdated
Show resolved
Hide resolved
baseline-error-prone/src/main/java/com/palantir/baseline/errorprone/RawTypes.java
Outdated
Show resolved
Hide resolved
Supportive of this check as well, thanks for putting it together @AlexLandau :-) |
@dansanduleac Yes, I've been testing this against the big monorepo. Thanks for taking care of the changelog. @carterkozak Thanks for the suggestions! |
lgtm, thanks! 👍 |
Released 3.2.0 |
This adds an ErrorProne check that fails when it detects raw types. Currently, javac has a built-in warning type for this, but it's not as flexible as ErrorProne; for example, you can't fail on raw-types errors without also failing on deprecation warnings, and you can't add exemptions for generated code.
Upstream ErrorProne doesn't seem to have any check for this or requests for such a check, beyond this issue: google/error-prone#253
For @SuppressWarnings, the check respects "rawtypes", which is already used by javac and Eclipse.
The current level is "warning"; feel free to change that.
I added the check to the BaselineErrorProneExtension due to seeing it in another PR adding a check.