       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.
-
-      Piping 0-arity functions might be considered a valid exception to this rule
-
-      This example ...
-
-        my_function()
-        |> my_other_function()
-
-      ...could be considered easier to read than ...
-
-        my_other_function(my_function())
-
-      Because of this, the check can optionally ignore such cases (see configuration options).
       """,
       params: [
-        allow_0_arity_functions: "Piping local or foreign 0-arity functions is allowed."
+        allow_0_arity_functions: "Allow 0-arity functions"
       ]
     ]
-
 
   @doc false
   @impl true

    issue_meta = IssueMeta.for(source_file, params)

    allow_0_arity_functions = Params.get(params, :allow_0_arity_functions, __MODULE__)



    {_continue, issues} =
      Credo.Code.prewalk(

    }
  end

  defp traverse({:|>, _, [{{:., _, _}, _, []}, _]} = ast, {true, issues}, _, true) do
    {ast, {false, issues}}
  end

  defp traverse({:|>, _, [{fun, _, []}, _]} = ast, {true, issues}, _, true) when is_atom(fun) do
    {ast, {false, issues}}
  end

  defp traverse({:|>, meta, _} = ast, {true, issues}, issue_meta, true) do
    {
      ast,
