Fl4m3Ph03n1x
Make `mix format` work with pipeline macros
Background
I use a library that defines a new pipeline macro, the triple arrow >>>. So in my code, it is normal to have something like this:
def safe_div(a, b), do:
a
|> divide(b)
>>> handle_result()
This magic here is in handle_result. What the >>> does is not important, what matters here is that this is a type of format that I want to see in my code.
Problem
The problem here is the mix format does not know how that it should treat >>> as it treats |>. So inevitably my code becomes:
def safe_div(a, b), do:
a
|> divide(b) >>> handle_result()
Which is very ugly and impossible to read for larger functions.
I have tried to find a way to change mix format’s configuration to fix this issue, unfortunately I was not able to find anything.
Question
- Can I configure
mix formatto treat>>>as a|>? - If not, would it be a bad idea to make a PR where people would be allowed to define “pipelike” operators/macros, thus telling
mix formathow to behave?
Basically, what options do I have here ?
Marked As Solved
josevalim
Here are the operators we consider pipeline like: elixir/lib/elixir/lib/code/formatter.ex at v1.11.4 · elixir-lang/elixir · GitHub
>>> isn’t one because it is also used as a Bitwise operator by Elixir.
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance








