-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
CustomImportOrder check broken #6386
Comments
@ringmaster217 I cannot reproduce your violations with the check from the google_config in master (https://github.com/checkstyle/checkstyle/blob/master/src/main/resources/google_checks.xml#L193-L197).
Please see https://checkstyle.org/report_issue.html#How_to_report_a_bug.3F .
We verify our configuration against the google style guide and not the formatter. |
I was able to reproduce the first post results with the google config from 2 years ago. 81ad459#diff-c55cd603ef6597463971db3f33f4f4c8
|
Because this has already been fixed for 2 years now I am closing the issue. |
When using the google java formatter with the google_checks.xml checkstyle configuration, checkstyle incorrectly flags import statements as being out of order. It appears that the CustomImportOrder module is incorrectly attempting to validate more import groups than are configured.
For example, this import block
produces this checkstyle output
It looks like the CustomImportOrder module is picking up the java.* imports as the STANDARD_JAVA_PACKAGE group, even though only STATIC and THIRD_PARTY_PACKAGE are configured in google_checks.xml. Packages imported after the java.* packages are then incorrectly flagged as being in the wrong group.
The text was updated successfully, but these errors were encountered: