On Wed, Jan 8, 2020 at 10:28 PM Eric Sunshine <sunshine@xxxxxxxxxxxxxx> wrote: > > advice seems simple on the surface, but every new piece of advice > means having to add yet another configuration variable, writing more > code, more tests, and more documentation This raises a question though, do we really need a new configuration for every new advice? So a user who's not interested in receiving advice will have to disable every single advice config? It doesn't seem scalable to me. I imagine a user will either want to enable or disable the advice feature all together. Why don't we have only one `enable_advice` configuration that controls all the advice messages? Thanks, Heba
