We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
list-diff
Hi, everyone.
I want to integrate goimports-reviser into our CI/CD to ensure that code gating will fail when the import ordering is not as expected.
goimports-reviser
But I found that list-diff flag is not work when a recursive path (./...) is given.
I am making a PR to fix this bug. But I have one question.
What is the right behavior when `list-diff` flag is given? Refact code and print file path? or only print file path?
From what I remember, when you run the goimports -l command, it only prints the file path without refactoring the code.
goimports -l
I don't know what behavior is expected here for goimports-reviser.
The text was updated successfully, but these errors were encountered:
Here is my PR #140
Sorry, something went wrong.
[#139] Find unformatted files in dir (Part 2) (#142)
ed23792
Use v3.6.0 tag with the fix
Successfully merging a pull request may close this issue.
Hi, everyone.
I want to integrate
goimports-reviser
into our CI/CD to ensure that code gating will fail when the import ordering is not as expected.But I found that
list-diff
flag is not work when a recursive path (./...) is given.I am making a PR to fix this bug. But I have one question.
From what I remember, when you run the
goimports -l
command, it only prints the file path without refactoring the code.I don't know what behavior is expected here for goimports-reviser.
The text was updated successfully, but these errors were encountered: