ForgeCredoChecks.FilterMap (forge_credo_checks v0.3.0)

Copy Markdown View Source

Basics

This check is disabled by default.

Learn how to enable it via .credo.exs.

This check has a base priority of high and works with any version of Elixir.

Explanation

Replace Enum.filter/2 |> Enum.map/2 with a comprehension.

Why

The pipe walks the list twice and allocates an intermediate list of matching elements before mapping. A comprehension does both in one pass, preserves order naturally, and avoids the reduce + reverse anti-pattern (paying a second traversal just to undo the order an accumulator imposed).

How to fix (in order of preference)

Preferred: comprehension.

# BEFORE
things
|> Enum.filter(&keep?/1)
|> Enum.map(&transform/1)

# AFTER
for x <- things, keep?(x), do: transform(x)

One pass, in-order, no intermediate list, no reverse step.

Last resort: Enum.reduce/3. Only when a comprehension is awkward and the consumer does not care about order (Map.new, Enum.sum, set membership, sort, count):

Enum.reduce(things, [], fn x, acc ->
  if keep?(x), do: [transform(x) | acc], else: acc
end)

What NOT to do

Do not switch to Enum.reduce/3 and append |> Enum.reverse/1 to restore order. That is exactly the tax the comprehension exists to avoid: you pay a second pass just to undo the [h | acc] reversal. If you need ordered output, use a comprehension.

Check-Specific Parameters

There are no specific parameters for this check.

General Parameters

Like with all checks, general params can be applied.

Parameters can be configured via the .credo.exs config file.