I read and agree with the basic principle outlined there. I can definitely see the issue with an ever growing list of options, especially those that would allow for code to diverge quite a bit in the look between applications. There does need to be consistency.
At the same time, I am also an advocate for readability of code. I was hoping that what would end up being a minor change, it wouldn't mean breaking apart lines like some of the things the formatter already does, would be a conversation worth having if it would mean engineers could read their code easier. On Tuesday, February 5, 2019 at 10:46:42 AM UTC+1, wojte...@plataformatec.com.br wrote: > > Hi Chris, > > To quote one of the design principles behind the formatter [1] > > > The second principle is to provide as little configuration as possible. > This eases the formatter adoption by removing contention points while > making sure a single style is followed consistently by the community as a > whole. > > For this reason, I think the proposal is unlikely to be accepted. > > [1] https://hexdocs.pm/elixir/Code.html#format_string!/2-design-principles > > -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to elixir-lang-core+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/bd452d84-a2ff-48e3-b253-cb9e8f813c53%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
