smarter handling of DRY checks about elvis_core HOT 5 CLOSED

+1. I've add this more than once and even referred it to @jfacorro recently.

from elvis_core.

I can definitely see the unnecessary pain elvis causes here. A different approach that makes sense would be very welcome! 😄

from elvis_core.

Maybe inaka/elvis#529 can eventually help.

from elvis_core.

Upping complexity would prevent this but then other more valid claims are perhaps ignored.

In the uses cases @Licenser describes this was my worry, so I did end up creating a function just to return a list. @jfacorro wasn't even "comfortable" that elvis was "forcing" the consumer to do this, but it was a one-time thing.

Apart from "simple" lists and "simple" tuples (e.g. those that contain only "variables" or "constant", but nothing "dynamic") do you see the need to ignore anything else?

@Licenser?

from elvis_core.

Maybe inaka/elvis#529 can eventually help.

Or (to some extent) ignoring a rule based on {module(), function(), arity()}.

from elvis_core.