improvement: suggested fixes for IllegalSafeLoggingArgument check #2133
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
carterkozak
reviewed
Mar 25, 2022
...e-error-prone/src/main/java/com/palantir/baseline/errorprone/IllegalSafeLoggingArgument.java
Show resolved
Hide resolved
|
Released 4.79.0 |
This was referenced Mar 26, 2022
Merged
bulldozer-bot bot
pushed a commit
to palantir/witchcraft-api
that referenced
this pull request
Mar 26, 2022
###### _excavator_ is a bot for automating changes across repositories. Changes produced by the roomba/latest-baseline-oss check. # Release Notes ## 4.79.0 | Type | Description | Link | | ---- | ----------- | ---- | | Improvement | suggested fixes for IllegalSafeLoggingArgument check | palantir/gradle-baseline#2133 | To enable or disable this check, please contact the maintainers of Excavator.
This was referenced Mar 26, 2022
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.
Follow-up to #2127.
In cases where validation would fail specifically due to calls to
SafeArg#ofwhere the argument was marked asUnsafe, suggest usingUnsafeArg#ofinstead==COMMIT_MSG==
suggested fixes for IllegalSafeLoggingArgument check
==COMMIT_MSG==
Possible downsides?