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
Create a Checkstyle module to enforce comment formatting in input files #13797
Comments
@relentless-pursuit do you have a suggestion on which checkstyle module we can use for this? It would be good to add an example that loosely follows our bug report format to help the person that works on this issue to fully understand what we need to do. |
I also like space after To find it , we can just remove space after // and see what Check is doing violation |
I used a Below it the example i tested the check:
Result of the build:
|
please send PR. |
… formatting in input files
… formatting in input files
… formatting in input files
Hi @romani , can this be assigned a hacktober fest label? |
@relentless-pursuit , please let us know what label matters this year. |
hacktoberfest i guess. i can only confirm if one of my such labeled PR gets merged. (among the two labels seen) |
Closed via #13803 |
@relentless-pursuit thanks for this! |
We haveve noticed inconsistencies in the formatting of single-line comments in the codebase. For instance, some comments lack a space after the //, making them harder to read.
Current Behavior:
Comments like
//violation
exist in the codebase without a space after//
.Desired Behavior:
All single-line comments should have a space after
//
, like// violation
.The text was updated successfully, but these errors were encountered: