You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- "dataModel JabRef52"- + " only supports pageInfo for the last citation of a group");+ LOGGER.warn("dataModel JabRef52" + " only supports pageInfo for the last citation of a group");
(For this, I can do a work-around by using single-line strings only)
timtebeek
changed the title
Make it compatible with Google Java Foramt
Prevent unintentional changes in logging best practices that conflict with Google Java Format
Oct 6, 2024
Are there additional changed out of view from the diff above that would explain why changes are reported in the first place?
For both cases I suppose the best way to see these resolved is to replicate them in a minimal draft PR unit test, and then from there ensure the prefix is retained for the ChainStringBuilderAppendCalls case for instance.
What problem are you trying to solve?
I want to use Google Java Format (AOSP) together with OpenRewrite
Describe the solution you'd like
OpenRewrite should not write files if only whitespace change.
Have you considered any alternatives or workarounds?
Disabling rules.
Additional context
org.openrewrite.staticanalysis.ChainStringBuilderAppendCalls
:org.openrewrite.java.logging.slf4j.ParameterizedLogging
(For this, I can do a work-around by using single-line strings only)
Are you interested in contributing this feature to OpenRewrite?
The text was updated successfully, but these errors were encountered: