-
Notifications
You must be signed in to change notification settings - Fork 135
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
Require safety propagation based on getters #2218
Conversation
Generate changelog in
|
// This will be promoted after an initial rollout period | ||
severity = BugPattern.SeverityLevel.SUGGESTION, |
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.
This is currently SUGGESTION
so I can excavate fixes in a way that's decoupled from baseline upgrades.
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.
Nice!
Released 4.112.0 |
###### _excavator_ is a bot for automating changes across repositories. Changes produced by the roomba/latest-baseline-oss check. # Release Notes ## 4.112.0 | Type | Description | Link | | ---- | ----------- | ---- | | Improvement | `SafeLoggingPropagation` error-prone check propages log-safety annotations from getters and superclasses/superinterfaces to the type level | palantir/gradle-baseline#2218 | To enable or disable this check, please contact the maintainers of Excavator.
==COMMIT_MSG==
Require log-safety annotation propagation based detected getters and superclasses/superinterfaces
==COMMIT_MSG==
We combine the safety of superclasses, as well as getters (non-static methods with zero parameters and non-void return type) to estimate the safety of a class. We only apply unsafe/do-not-log annotations as this heuristic is not exhaustive, so we bias toward cases in which we're confident we can be safer.