@romani @mohitsatr please review this PR

@romani please review

@romani please review this PR

@romani please review

My concern is that this is Google's style issue, but fix is done in general implementation.
Others might not like this behavior.

@vivek-0509, please share your thoughts on this update

@vivek-0509 please review, I have changed the fix to only concern Google's style

@romani
I agree with the concern, we should not modify the IndentationCheck for this. It's a general-purpose check, and this column-0 text block allowance is specific to Google's style guide. The OpenJDK style guide (v6) and Sun/Oracle convention have no such rule, and we will likely add this check in both those check config files in the future.

i think this can be achieved through a SuppressionXpathSingleFilter in google_checks.xml instead.
Also, looking at the changes done in the PR to make it customizable for Google style by adding a new property and keeping the default to false for other cases, but the fix only modifies shouldProcessTextBlockLiteral() in LineWrappingHandler, this only covers some cases and looks like a partial fix. Cases stated below will still have violations, but generally are rare cases but we should cover them

getData(
"""
        content
""",
        5);

public String getQuery() {
    return     
"""                 //  column 0, this is what gets flagged
returned content
""";                //  column 0, also flagged
}

Lets try the SuppressionXpathSingleFilter approach if we can achieve this through that.
What do you think ??

@Anushreebasics You can close the PR the issue is resolved

@Anushreebasics, please create issue on Indentation Check, with default confirmation .

We need to detach your update from Google style.
New property might make sense, let's review it from start with new issue.

We can close this PR, for now. Code can be reused in new PR for new issue.