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
ExplicitItLambdaParameter has two different responsabilities. One that it is not redundant on lambda with just one parameter and forbid parameters called it on lambda that have more than one parameter.
I think that we should split those two responsabilities in two different rules
Context
I like a rule that flags unnecessary it declarations but I want to be able to use it as a name for my lambda. An example is forEachIndexed { index, it-> }. If I'm OK with using it on forEach the indexed shouldn't change that.
For that reason I want to split this rule. To enable one and disable the other.
The text was updated successfully, but these errors were encountered:
Expected Behavior of the rule
ExplicitItLambdaParameter
has two different responsabilities. One thatit
is not redundant on lambda with just one parameter and forbid parameters calledit
on lambda that have more than one parameter.I think that we should split those two responsabilities in two different rules
Context
I like a rule that flags unnecessary
it
declarations but I want to be able to useit
as a name for my lambda. An example isforEachIndexed { index, it-> }
. If I'm OK with usingit
onforEach
the indexed shouldn't change that.For that reason I want to split this rule. To enable one and disable the other.
The text was updated successfully, but these errors were encountered: