-
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
Automatically fix AssertNoArgs #1967
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Generate changelog in
|
pkoenig10
approved these changes
Nov 9, 2021
Released 4.40.0 |
This was referenced Nov 9, 2021
Merged
bulldozer-bot bot
pushed a commit
to palantir/witchcraft-api
that referenced
this pull request
Nov 9, 2021
###### _excavator_ is a bot for automating changes across repositories. Changes produced by the roomba/latest-baseline-oss check. # Release Notes ## 4.38.0 | Type | Description | Link | | ---- | ----------- | ---- | | Improvement | Improve Zero Warmup Rate Limiter to Catch Int Literals | palantir/gradle-baseline#1960 | ## 4.39.0 | Type | Description | Link | | ---- | ----------- | ---- | | Fix | The `com.palantir.baseline-java-versions` plugin requires gradle 7 and fails eagerly on older versions. Previously it would cause non-obvious failures later depending on task execution. | palantir/gradle-baseline#1965 | | Feature | Add Error Prone check to prefer `hasNoArgs` on service exception asserts and loggable exception asserts. | palantir/gradle-baseline#1966 | ## 4.40.0 | Type | Description | Link | | ---- | ----------- | ---- | | Improvement | Automatically fix AssertNoArgs | palantir/gradle-baseline#1967 | To enable or disable this check, please contact the maintainers of Excavator.
This was referenced Nov 9, 2021
This was referenced Nov 9, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After this PR
==COMMIT_MSG==
Automatically fix AssertNoArgs
==COMMIT_MSG==
Possible downsides?
Some risk that this will flag projects on older versions of safe-logging if baseline upgrades first. In that case, we'd still be producing warnings, so either way isn't ideal.