@smita1078 @romani please review

@vivek-0509 , what do you think about this update?

@romani As we discussed before the core problem in this issue that we need to solve is a cyclic dependency between IndentationCheck and its handler classes. Currently every handler, AbstractExpressionHandler and all its subclasses, as well as LineWrappingHandler and DetailAstSet holds a private final IndentationCheck indentCheck field and actively calls back into the Check to read configuration values (getBasicOffset(), getBraceAdjustment() etc..), to access source lines (getLine(lineNo)), to report violations (indentationLog()). At the same time IndentationCheck creates, owns, and orchestrates all these handlers. So both sides know about each other, the Check knows handlers and handlers know the Check, which is the cycle we need to break. The same cycle exists in LineWrappingHandler and DetailAstSet ,LineWrappingHandler holds IndentationCheck directly and calls getLineWrappingIndentation(), isForceStrictCondition(), getLine(), etc on it, while DetailAstSet
calls getLine() and getIndentationTabWidth() on it.

Before we write a single line of code we need to agree on a proper solution for this, since it is a big refactoring work of the most complex check we have.

@Anushreebasics if you are interested about solving this issue i would suggest you to understand the working of the indentation check then you can propose you solution and we can than discuss from there. you can also take reference from the discussion we had earlier here