Replace direct System.out usage with SLF4J logging (java:S106) - #10
Draft
trly wants to merge 1 commit into
Draft
Conversation
Addresses SonarQube java:S106 by adding an SLF4J logger to each affected class and routing all standard-output writes through it.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Resolves SonarQube rule
java:S106— Standard outputs should not be used directly to log anything.Changes in this repository:
org.slf4j:slf4j-api(with theslf4j-simpleruntime binding) tobuild.gradle.private static final Logger LOGGERin each affected class.System.out.printfcall as a parameterizedLOGGER.info(...)call, preserving theoriginal numeric formatting via
String.formatwhere a format specifier was significant.No program logic or visible output values were changed.
Created by Sourcegraph agentic batch change.