Running the new Elixir formatter

[NobbZ]

@josevalim

There are two things: we don’t want projects to have many formatter related files. So between adding a .formatter.exs or .external_formatter.exs to source control, I would rather keep the first and have a single file.

In my suggestion, only .formatter.exs is added to the VCS, the external one can get regenerated.

@josevalim

And the second is that loading and parsing the Mixfile.project is going to add a bunch of indirection if all we want to load the formatter options.

You don’t do it when loading the generator options, but when deps.getting or deps.compileing. From the gathered information you then generate the external file.

@josevalim

Yes but then you have things like the phoenix_ecto project which exists to manage the ecto dependencies for you in regards to phoenix

Thats indeed a problem. But then again, those projects could publish the rules of their direct dependencies explicitely. And since the API to fetch those is specified, it can be even done programmatically.