I often wish they were _less_ configurable. Even Black's handful of config options are too many... Each one is a chance to pick a whole new color for the bikeshed.
That makes sense, but it's a problem when the formatter makes a rather opinionated choice and doesn't allow one to configure it. The primary example I'm thinking of in Elixir is comments for pipelines.
For example, if I use the pipe example on Elixir's landing page and add comments to it (obviously a contrived example):
"Elixir" # string to get frequencies for
|> String.graphemes() # Get all graphemes (i.e., character units)
|> Enum.frequencies() # Get the number of occurrences of each grapheme
This gets formatted by the Elixir formatter to:
# string to get frequencies for
"Elixir"
# Get all graphemes (i.e., character units)
|> String.graphemes()
# Get the number of occurrences of each grapheme
|> Enum.frequencies()
This is a rather strongly opinionated format stance, and as far as I know, it's not configurable.
For example, if I use the pipe example on Elixir's landing page and add comments to it (obviously a contrived example):
This gets formatted by the Elixir formatter to: This is a rather strongly opinionated format stance, and as far as I know, it's not configurable.