Can confirm, I use pipe into case a ton. My only complaint about it is that vscode-elixir highlighting doesn’t respect that pattern 
ityonemo
0
lud
I use |> case do a lot but always when I actually have to match against several patterns. I did not think about using it just to transform a value. Stupid me 
Anyway I have a small library that I use to bundle all the small utilities I made to work with elixir. I have a public version but with only 2 utilities. I have added a ~> macro to it. I use ~> and not |= because this operator is not available.
0
OvermindDL1
Wait what? It’s bog-standard normal elixir syntax and it absolutely should be accepted. That sounds like a bug. The highlighting works fine in emacs and intellij-elixir at least… o.O
0
sorentwo
Oban Core Team
It highlights just fine in vim. However, the formatter insists on expanding it from a single line to three.
That’s my only complaint 
0
OvermindDL1
sorentwo
Oban Core Team
OvermindDL1
Sadly the elixir formatter is really opinionated and unchangeable. ^.^;
freedom_formatter has more options, it’s a fork of elixir’s formatter, can PR into it! ^.^
0
ityonemo
to be more specific, it thinks that case is a function because it’s at the end of a pipe, and so it highlights it as a function call, and not a keyword. I’m being super nitpicky. It’s always the little things that drive you insane, mirite?
1
pera
defmacro {:|>, _line, [pipe, match]} ~> expr do
quote do
unquote(pipe)
|> case do unquote(match) -> unquote(expr) end
end
end
defmacro _ ~> _, do: raise ArgumentError, "~>/2 must be presided by a pipe"
{1,2} |> {x,y} ~> {x+1, foo(y)} etc… 
4