> > Ah, but the _reason_ you're making this change is that you don't consider > it to be > a Best Practice.
No, that's not the reason. config/config.exs is totally fine in certain use cases. Furthermore, config/config.exs is totally valid for *all applications*. The check you are asking would be a false positive for the huge majority of Elixir projects out there. Here is a better example. Imagine that in all applications generated by mix.new, we had a macro as an example: defmodule Hello do defmacro world, do: :ok end Is that code wrong? Definitely not. But we can decide to not start a new app with a macro as an example (as there are better options). > I haven't been tracking changes closely, so I can't give you any other > specifics. > And really, that is kind of my point. As a programmer using the Elixir > tooling, > I shouldn't _have_ to track changes closely: > I understand your point. But please understand that the lack of other examples do not help move this discussion forward. I personally cannot think of any use case for the proposed warning/check, so unless someone presents a counter- argument or another example, there isn't anything to change. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/CAGnRm4LQRRMCab2amUKHrUKrSnhpB2HOw5FU4uMJ1akPad5sSw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
