It now formats it to:
defrule parse_entry(
seq([
parse_type(),
parse_body()
])
),
pipe_result_into:
List.to_tuple()
|> (case do
{:started, datetime_string} ->
{:started, parse(datetime_string, parse_weirddatetimeformat()).result}
result ->
result
end)
Looks much more readable like that. 
Still far far too right (I’ve never seen the point to aligning to something above like that, only for repeated calls or so, which this is not the case, thus only indentation should be used, not alignment), and that random newline in the case is jarring, it either needs to be gone, or perhaps made into this (which I do in my especially large case statements, of which this is not one so I would not have empty lines at all):
defrule parse_entry(
seq([
parse_type(),
parse_body()
])
),
pipe_result_into:
List.to_tuple()
|> (case do
{:started, datetime_string} ->
{:started, parse(datetime_string, parse_weirddatetimeformat()).result}
result ->
result
end)
EDIT:
@josevalim Fix formatting of multiline "foo.{...}" calls by whatyouhide · Pull Request #6979 · elixir-lang/elixir · GitHub just went through, it formats:
alias Foo.{
Bar
}
As this instead now:
alias Foo.{
Bar
}
Isn’t that the same thing that I want from this:
defrule parse_entry(
seq([
parse_type(),
parse_body()
])
)
Wanting it to be this:
defrule parse_entry(
seq([
parse_type(),
parse_body()
])
)
Seems the same kind of issue to me? And as such that PR becomes inconsistent considering the above case is not done too?
(Although I’d still put the trailing comma too as without it looks inconsistent and wrong).
