Reading José's recent blog What’s new in Elixir – Apr/19 http://blog.plataformatec.com.br/2019/04/whats-new-in-elixir-apr-19
made me think about a possible enhancement to "mix xref deprecated". Specifically, I'd like it to warn me about deprecated practices in file system organization and use. For example, José says that > The first change is that we will no longer generate config/config.exs > for projects generated with mix new. Relying on configuration is > undesired for most libraries and the generated config files pushed > library authors in the wrong direction. Furthermore, mix new > --umbrella will no longer generate a configuration for each child app; > instead, all configuration should be declared in the umbrella root. > That’s how it has always behaved, we are now making it explicit. Mix could help us pull existing projects into compliance by telling us about it when they contain deprecated file usage. To be clear, I don't really care if the relevant command string is "mix xref deprecated"; I just want a quick, informative report on things I should address. -r -- 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/54F4BD70-FD3F-410B-9F21-17450861EFDC%40gmail.com. For more options, visit https://groups.google.com/d/optout.
