Describe the bug
When you reformat the code with mix format via the plugin, it does not read/use the .formatter.exs that's in the project directory. Because it doesn't use the project's .formatter.exs, dependencies that also have their own formatters are also not considered.
Example of running mix format in the project
field :something, type: non_null(:something) do
arg :some_id, non_null(:id)
arg :another_id, non_null(:id)
Example of running mix format outside the project (eg. having the plugin run it)
field :something, type: non_null(:something) do
arg(:some_id, non_null(:id))
arg(:another_id, non_null(:id))
To Reproduce
Steps to reproduce the behavior:
Reformat the code as usual.
ensuring that the plugin's mix format runs
Expected behaviormix format from the plugin to produce the same output as running mix format inside the project folder.
Logs
Enabling the IntelliJ logs to output log levels :all and it reveals the plugin attempts to run the following.
Describe the bug When you reformat the code with
mix format
via the plugin, it does not read/use the.formatter.exs
that's in the project directory. Because it doesn't use the project's.formatter.exs
, dependencies that also have their own formatters are also not considered.Example of running
mix format
in the projectExample of running
mix format
outside the project (eg. having the plugin run it)To Reproduce Steps to reproduce the behavior:
mix format
runsExpected behavior
mix format
from the plugin to produce the same output as runningmix format
inside the project folder.Logs Enabling the IntelliJ logs to output log levels
:all
and it reveals the plugin attempts to run the following.Desktop:
Erlang:
Elixir:
Plugin: