Credo.Check.Readability.SinglePipe (Credo v1.6.0) View Source

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


Pipes (|>) should only be used when piping data through multiple calls.

So while this is fine:

|> Enum.take(5)
|> Enum.shuffle
|> evaluate()

The code in this example ...

|> evaluate()

... should be refactored to look like this:


Using a single |> to invoke functions makes the code harder to read. Instead, write a function call when a pipeline is only one function long.

Like all Readability issues, this one is not a technical concern. But you can improve the odds of others reading and liking your code by making it easier to follow.

Check-Specific Parameters

Use the following parameters to configure this check:


Allow 0-arity functions

This parameter defaults to false.

General Parameters

Like with all checks, general params can be applied.

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