Config. validation for no_output vs. verbose

[paulo-ferraz-oliveira]

I found myself writing a test for {verbose, true}, {no_output, true} and wonder if we shouldn't issue a warning in this case, for consistency.

I know verbose is for making the info. more, well, verbose, and no_output is probably for CI, but I think having what I was testing (as per above) is confusing, even with the README.

verbose states "more information will be printed"
no_output states "nothing will be printed"

Another way to look at this would be to merge the two options into e.g. verbosity, where we could have none | summary | detail, for example

[elbrujohalcon]

Merging the options would be my favourite choice.

[TBennett1]

Hey @elbrujohalcon and @paulo-ferraz-oliveira can I take a stab at this. I don't know if there are plans to fold this into #515 but I can either branch off of that or just do the work on current implementation. Thanks!

[elbrujohalcon]

I'll let @paulo-ferraz-oliveira speak in regard of #515, but… from my perspective: Sure, @TBennett1 , you can go for it. I would just recommend you to wait a few days so you can use it for #hacktoberfest: https://hacktoberfest.com/

[paulo-ferraz-oliveira]

Sorry for the late reply. #515 is out, and there were plans to include this.