Skip to content

automate the remediation of Checkstyle #34830

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

Closed
Pankraz76 opened this issue Apr 25, 2025 · 6 comments
Closed

automate the remediation of Checkstyle #34830

Pankraz76 opened this issue Apr 25, 2025 · 6 comments
Labels
status: duplicate A duplicate of another issue

Comments

@Pankraz76
Copy link

Pankraz76 commented Apr 25, 2025

Fixing violations by hand is tedious and error-prone - even though you gain experience, which Checkstyle is also kind of about.

It would be nifty to have a real autofix solution like OpenRewrite to properly address these issues: https://docs.openrewrite.org/running-recipes/popular-recipe-guides/automatically-fix-checkstyle-violations

Most programmers agree that having consistent formatting across a code base makes it easier to work with. Tools like Checkstyle provide automated enforcement of these policies. But it's never fun to have your workflow interrupted by complaints about formatting. This guide will show you how to configure OpenRewrite to automate the remediation of Checkstyle policy violations.

Either we wait for checkstyle/checkstyle#16948 or implement it ourselves quickly, like done in:

References:

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Apr 25, 2025
@bclozel bclozel marked this as a duplicate of #34818 Apr 26, 2025
@bclozel bclozel closed this as completed Apr 26, 2025
@bclozel bclozel added status: duplicate A duplicate of another issue and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Apr 26, 2025
@Pankraz76
Copy link
Author

Pankraz76 commented Apr 26, 2025

plz reopen, as this is the correct one. Thanks

Image

@bclozel
Copy link
Member

bclozel commented Apr 26, 2025

Isn't this superseded by the PR?
I am confused because you opened and closed a lot of issues.

@Pankraz76
Copy link
Author

yes im sorry lot of action happening. I can simply reopen a final new one or you reopen.

Lets have fresh new start: #34833

@bclozel
Copy link
Member

bclozel commented Apr 26, 2025

Another duplicate 😔
Is the PR related at all to that issue?

@Pankraz76
Copy link
Author

Pankraz76 commented Apr 26, 2025

technically yes, but only one active right now. Isn't it?
What PR you mean?

Image

@Pankraz76
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: duplicate A duplicate of another issue
Projects
None yet
Development

No branches or pull requests

3 participants