-
Notifications
You must be signed in to change notification settings - Fork 152
Consistently use SLF4J's recommended styles #992
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
Conversation
return StringHelper.convertToMultiValueMap(this.requestParameters); | ||
} | ||
|
||
public Logger log() { |
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.
is this used?
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.
No, and weirdly there are few other places where we have an unused getter for the Logger.
However, this PR was just meant to handle one very low-risk issue in bulk, and I will be handling unused methods like this in smaller, more focused PRs where it's easier to see if there are unintended side effects.
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.
Ok thanks. Suggest having a new task for removing unused methods if there isn't one already.
msal4j-sdk/src/main/java/com/microsoft/aad/msal4j/CloudShellManagedIdentitySource.java
Outdated
Show resolved
Hide resolved
msal4j-sdk/src/main/java/com/microsoft/aad/msal4j/MexParser.java
Outdated
Show resolved
Hide resolved
msal4j-sdk/src/main/java/com/microsoft/aad/msal4j/MexParser.java
Outdated
Show resolved
Hide resolved
…nagedIdentitySource.java Co-authored-by: Gladwin Johnson <90415114+gladjohn@users.noreply.github.com>
Co-authored-by: Gladwin Johnson <90415114+gladjohn@users.noreply.github.com>
Co-authored-by: Gladwin Johnson <90415114+gladjohn@users.noreply.github.com>
looks good @Avery-Dunn |
This PR refactors the logging throughout the codebase to be more consistent and efficient by following SLF4J's recommended styles.
Many classes received changes, but same two changes were made to each one:
private static final Logger LOG = ...
Only logging statements were affected and there were no changes to the actual messages that get logged, so the actual behavior of the library is unchanged.