You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ah ok, I didn't notice that rule "No assignment in if condition (ObsoleteNoAssignmentInIfConditionCleanUp.java)" existed.
So the idea would be to extend the principle to other expressions than if expressions, such as method invocations, array accesses,...
This new rule would be the equivalent of the one with increment/decrement inside expression.
https://github.com/JnRouvignac/AutoRefactor/blob/master/plugin/src/main/java/org/autorefactor/jdt/internal/ui/fix/ObsoleteIncrementStatementRatherThanIncrementExpressionCleanUp.java
As you may already know, Sonar raises a warning when assignement is inside an expression.
Example of non-compliant code candidate for refactoring
Desired refactoring result would be the Sonar-compliant version
Let me know you thoughts on it.
Would it be complicated to do?
The text was updated successfully, but these errors were encountered: