Github, generate report for Indentation/all-examples-in-one

Report for Indentation/all-examples-in-one:
https://checkstyle-diff-reports.s3.us-east-2.amazonaws.com/016e96a76d3ef484bf86b85a78df95e7cb1034fd_2026143035/reports/diff/index.html

Investigating the cases

Hi @romani
I have reviewed the diff report and believe the fix is working correctly. The newly flagged violations appear to be genuine indentation issues that were previously being missed due to the bug in LambdaHandler.getIndentImpl().

For example, the new violation in https://checkstyle-diff-reports.s3.us-east-2.amazonaws.com/016e96a76d3ef484bf86b85a78df95e7cb1034fd_2026143035/reports/diff/openjdk25/index.html#A1:

        FILE_ASSOCIATIONS ("file-associations",
                OptionCategories.PROPERTY, () -> {
            Map<String, ? super Object> args = new HashMap<>();  // column 12

The lambda () -> { appears inline after OptionCategories.PROPERTY which starts at column 16. Therefore, the lambda body should be at 16+4=20, but it's at column 12. This is genuinely incorrect indentation that was being overlooked before.

The current fix uses ENUM_CONSTANT_DEF as the base, which calculates expected body indentation as 16 (enum constant 8 + lineWrapping 4 + basicOffset 4). For inline lambdas, this is slightly lower than the visually ideal 20. However, with forceStrictCondition=false (default), both 16 and 20 are acceptable. Once we align on this fix and confirm there are no false positives, I can explore adding stricter handling for inline lambdas as a follow up enhancement.

Please review the diff report and let me know if any of the newly flagged violations appear to be false positives or if I am missing something.

Additionally, the fix also resolves false positives for correctly indented code.
I tested a block lambda with statements in an enum constant on the master branch

public enum TestLambdaEnumBlock {
    VALUE(
        () -> {
            System.out.println("test");
        }
    );

    TestLambdaEnumBlock(Runnable runnable) {
    }
}

Result on master (without fix):

Starting audit...
[ERROR] TestLambdaEnumBlock.java:4:9: 'lambda arguments' has incorrect indentation level 8, expected level should be 12. [Indentation]
[ERROR] TestLambdaEnumBlock.java:5:13: 'block' child has incorrect indentation level 12, expected level should be 16. [Indentation]
[ERROR] TestLambdaEnumBlock.java:6:9: 'block rcurly' has incorrect indentation level 8, expected level should be 12. [Indentation]
Audit done.
Checkstyle ends with 3 errors.

However, this code Is correctly indented:

• Lambda at column 8 = enum constant (4) + lineWrappingIndentation (4)
• Body at column 12 = lambda (8) + basicOffset (4)
• Closing brace at column 8 = matches lambda

This example shows that the original code produces false positives for block lambdas with statements in enum constants.

Please trigger diff test on all examples config

@romani I have already triggered Github, generate report for Indentation/all-examples-in-one.
Here is the report link: https://checkstyle-diff-reports.s3.us-east-2.amazonaws.com/016e96a76d3ef484bf86b85a78df95e7cb1034fd_2026143035/reports/diff/index.html

Could you please clarify which specific config you'd like me to test with? Is there a different command I should use?

@romani ping