You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In v0.8.0, text coloring was introduced which I generally am a great fan of. Having it in usage strings seems like something I definitely want to have.
The first implementation of it applies it to the entire output of the usage string, which doesn't help one to focus on what's actually the problem.
Therefore I would recommend to use color (and/or bold text) only to highlight portions of it, like the required parameters that were missing. This could also be used to highlight suggestions in a friendly color.
Of course, a disclaimer shall be placed here that this is a somewhat cosmetical issue which is to some extend subjective. This issue is nothing more than a suggestion.
As a side-note, thanks for implementing everything with dependencies in a feature-gated fashion to allow an opt-out, which is what I chose as an intermediate solution in my case. Generally, that's a great practice that I will adopt were adequate as well.
The text was updated successfully, but these errors were encountered:
I agree. Perhaps the entire string being red is a bit much. I want avoid having rainbow output though where errors are one color, suggestions another, regular out another, etc. Perhaps a good middle ground would be the error and suggestions are red, the usage and "for more information" string are regularly formatted.
In v0.8.0, text coloring was introduced which I generally am a great fan of. Having it in usage strings seems like something I definitely want to have.
The first implementation of it applies it to the entire output of the usage string, which doesn't help one to focus on what's actually the problem.
Therefore I would recommend to use color (and/or bold text) only to highlight portions of it, like the required parameters that were missing. This could also be used to highlight suggestions in a friendly color.
Of course, a disclaimer shall be placed here that this is a somewhat cosmetical issue which is to some extend subjective. This issue is nothing more than a suggestion.
As a side-note, thanks for implementing everything with dependencies in a feature-gated fashion to allow an opt-out, which is what I chose as an intermediate solution in my case. Generally, that's a great practice that I will adopt were adequate as well.
The text was updated successfully, but these errors were encountered: