Remove warnings about missing EEx

[RobertDober]

This should us rid of

==> benchfella
Compiling 9 files (.ex)
warning: EEx.compile_file/2 defined in application :eex is used by the current application but the current application does not depend on :eex. To fix this, you must do one of:

  1. If :eex is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :eex is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :eex, you may optionally skip this warning by adding [xref: [exclude: [EEx]]] to your "def project" in mix.exs

  lib/mix/tasks/bench_graph.ex:93: Mix.Tasks.Bench.Graph

[cognivore]

I would humbly advice to run mix format mix.exs, commit and git rebase -i, then force-push into your PR branch to fix this excessive indentation.

[RobertDober]

OMG how did that happen :(

[RobertDober]

fix coming up

[cognivore]

I'm not entirely sure that with newer Elixirs applications: is obligatory even.
Consider [a patch that fixes similar issue in inch_ex.

I would just leave extra_applications: [:eex]. I think it would be wise to also verify why does this supress the warning.

My hypothesis is that it has to do with the fact that newer Elixirs now know how to assemble minimal releases, but need a little help with figuring out which bits and bobs from the full Elixir distribution to include, but I'm not 💯% sure...

[RobertDober]

I do not know I very simply did what the warning said 🤷

[RobertDober]

but looking at the link you provided I would say they just did the same, no?

[cognivore]

Not quite. Note how inch_ex dropped applications key entirely.

[RobertDober]

you can do that too of course I will not complain, is there any action on my side yet?

[cognivore]

@RobertDober I don't think so, now we wait for the maintaners, hah.