-
Notifications
You must be signed in to change notification settings - Fork 854
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
Removing unused imports leaves extra blank line after package statement, isn't idempotent #598
Labels
Comments
Allc9001
changed the title
edge case where google java formatter not Idempotence
edge case where google java formatter is not idempotence
Apr 22, 2021
Allc9001
changed the title
edge case where google java formatter is not idempotence
edge case where google java formatter is not idempotent
Apr 22, 2021
Thanks for finding this. We would agree that any non-idempotence is a bug. Since it at least reaches a fixed point quickly (it's like "idempotence, once removed") it might not be a high-priority fix, but we're glad to keep this open until then. |
cushon
changed the title
edge case where google java formatter is not idempotent
Removing unused imports leaves extra blank line after package statement, isn't idempotent
Dec 11, 2023
This was referenced Dec 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a class that if I format it twice with google java formatter it will produce 2 different results. This is not what I would expect - I would think that you can format a file any number of times and google java formatter should always produce the exact same result. Is my assumption wrong ?
Here is an example:
original class:
If I then format it I get this:
And if I format it again I get this (it's removed an extra space):
The text was updated successfully, but these errors were encountered: