@Zopsss , please make PR with Input that shows shows long identifiers wrapped by formatter as he can AND how checkstyle violate them.

Long variable, method, type name, ... Give a bit more examples. Keep it formatted by formatter.
attention to example with a lot of nested code and lond identifier (20 characters) in most deep point of it. So it is not very long but still line with 100 can not fit it.

we should revisit the working of LineLength module and add a new property to ignore long identifiers,

it is not that easy, LineLength become not Java Check, so it does not know anything about methods and variables.

points of attention ....aaaaaaaaaaa = and ...tttttttttt() {
so tool does not break other rules for "=" and { to do line wrapping.

The only solution I see is to allow users to use suppressions to mark suppression in comment and explain reason https://checkstyle.org/google_style.html#Google_Suppressions, please play with this and lets choose what we would recomment for users to use if they run into this.

@Zopsss , please make PR with Input that shows shows long identifiers wrapped by formatter as he can AND how checkstyle violate them.

Long variable, method, type name, ... Give a bit more examples. Keep it formatted by formatter. attention to example with a lot of nested code and lond identifier (20 characters) in most deep point of it. So it is not very long but still line with 100 can not fit it.

Umm creating a separate PR won't help much, I think it will be better to show the code here with the output, I guess this will be a more efficient way.

Original code:

/** some javadoc. */
public class TestingColumnLimit {
  public static int GLLLLLLLLLLLLLLLLLLOOOOOOOOOOOOOOOBBBBBBBBAAAAAAAAALLLLLLLLLLL_______VARRRRRRRIIIIIIIABLEEEEEEEEE = 99;

  final int abccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc = 99;

  void fooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo() {

    boolean xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx = true;

    if (xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx) {
      // some code
    } else {
      // some code
    }

    switch (GLLLLLLLLLLLLLLLLLLOOOOOOOOOOOOOOOBBBBBBBBAAAAAAAAALLLLLLLLLLL_______VARRRRRRRIIIIIIIABLEEEEEEEEE) {
        case abccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc:
            fooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo();
            break;

        default:
            break;
    }

    System.out.println("Helllllllllllllllllllllllllllllllllllllllllllllllllllllllllloooooooooooooooooooooooooooooooooo");
  }

  class Innnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnneeeeeeeeeeeeeeeeeeeeeeeerrrrrrrrrrrrrrrrrrrr {}
}

Formatted code:

/** some javadoc. */
public class TestingColumnLimit {
  public static int
      GLLLLLLLLLLLLLLLLLLOOOOOOOOOOOOOOOBBBBBBBBAAAAAAAAALLLLLLLLLLL_______VARRRRRRRIIIIIIIABLEEEEEEEEE =
          99;

  final int
      abccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc =
          99;

  void
      fooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo() {

    boolean
        xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx =
            true;

    if (xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx) {
      // some code
    } else {
      // some code
    }

    switch (GLLLLLLLLLLLLLLLLLLOOOOOOOOOOOOOOOBBBBBBBBAAAAAAAAALLLLLLLLLLL_______VARRRRRRRIIIIIIIABLEEEEEEEEE) {
      case abccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc:
        fooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo();
        break;

      default:
        break;
    }

    System.out.println(
        "Helllllllllllllllllllllllllllllllllllllllllllllllllllllllllloooooooooooooooooooooooooooooooooo");
  }

  class Innnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnneeeeeeeeeeeeeeeeeeeeeeeerrrrrrrrrrrrrrrrrrrr {}
}

Output:

$ java -jar .\checkstyle-10.17.0-all.jar -c .\google_checks.xml .\TestingColumnLimit.java
Starting audit...
[WARN] \TestingGoogleStyle\.\TestingColumnLimit.java:4: Line is longer than 100 characters (found 105). [LineLength]
[WARN] \TestingGoogleStyle\.\TestingColumnLimit.java:8: Line is longer than 100 characters (found 111). [LineLength]
[WARN] \TestingGoogleStyle\.\TestingColumnLimit.java:12: Line is longer than 100 characters (found 106). [LineLength]
[WARN] \TestingGoogleStyle\.\TestingColumnLimit.java:15: Line is longer than 100 characters (found 106). [LineLength]
[WARN] \TestingGoogleStyle\.\TestingColumnLimit.java:18: Line is longer than 100 characters (found 107). [LineLength]
[WARN] \TestingGoogleStyle\.\TestingColumnLimit.java:24: Line is longer than 100 characters (found 112). [LineLength]
[WARN] \TestingGoogleStyle\.\TestingColumnLimit.java:25: Line is longer than 100 characters (found 115). [LineLength]
[WARN] \TestingGoogleStyle\.\TestingColumnLimit.java:26: Line is longer than 100 characters (found 107). [LineLength]
[WARN] \TestingGoogleStyle\.\TestingColumnLimit.java:34: Line is longer than 100 characters (found 106). [LineLength]
[WARN] \TestingGoogleStyle\.\TestingColumnLimit.java:37: Line is longer than 100 characters (found 122). [LineLength]
Audit done.

Formatter tries to shrink down the line size but it still crosses the limit of 100.

we should revisit the working of LineLength module and add a new property to ignore long identifiers,

it is not that easy, LineLength become not Java Check, so it does not know anything about methods and variables.

points of attention ....aaaaaaaaaaa = and ...tttttttttt() { so tool does not break other rules for "=" and { to do line wrapping.

The only solution I see is to allow users to use suppressions to mark suppression in comment and explain reason https://checkstyle.org/google_style.html#Google_Suppressions, please play with this and lets choose what we would recomment for users to use if they run into this.

I think the SuppressWarningsFilter would be a good choice to recommend it to users, users' will just need to use SuppressWarnings annotation where they need suppression, something like:

  @SuppressWarnings({"LineLength"})
  final int abccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc = 99;

Edit: PR sent regarding this: #15426

@rdiachenko , do you agree with suppression?

@rdiachenko

@Zopsss , while we are waiting for @rdiachenko , please send PR with update of Inputs annotations to show how it will looks like for user.
Please also update coverage table to mention that user should use extra code update to avoid violation on such edge cases.

done #15460 @romani

LineLength become not Java Check, so it does not know anything about methods and variables

I missed this point. Makes sense. I'm good with using suppression.