`--no-ansi` is not stripping colours about claide

[fabiopelosin]

Closed by 6c7f6b3

[AliSoftware]

👍

[kylef]

Sorry guys, missed something with the yellow warning:

[fabiopelosin]

That happens during class evaluation much earlier than CLAide::Command::run

[fabiopelosin]

I don't have a well formed opinion about this yet... the options that I see are:

• Remove the colour form the warning
• Do nothing as it is a temporary problem
• Refactor to print the warnings in CLAide::Command::run

None of those look optimal to me.

[fabiopelosin]

I think that we shouldn't fix this as it is a temporary problem

[fabiopelosin]

Closing until someone weight-ins expressing a reason about why we should fix.

[alloy]

It’s temporary now, but other warnings will be introduced at some point, so it’s a recurring problem.

[fabiopelosin]

This problem doesn't affect all warnings but specifically this one because the warning is presented during the initialization of the concrete CLAide sub-classes: https://github.com/CocoaPods/CLAide/blob/master/lib/claide/command.rb#L502-L503

This happens before the machinery to handle the ANSI flag is setup. It is very unlikely that we encounter a similar warning. Moreover, handling it properly would require extensive changes to the architecture of CLAide (i.e. to parse and handle the --no-ansi flag before loading the classes of the concrete CLAide commands).

[fabiopelosin]

Another important thing to keep in mind is that the --no-ansi has been introduced to not pollute the standard output of the executables when used by a script (not for visual preference). The warnings are printed to the standard error stream and thus it is less relevant to strip the ANSI codes from them, although still desiderable for visual consistency.

[alloy]

I was actually thinking more of buffering such early warnings in a simple array and displaying them as soon as the options were parsed and evaluated. That might still be too much, but I think that an app like AppCode does not like ANSI, ever?

[fabiopelosin]

Good alternative. A bit annoying that we already do that in CocoaPods (to show warnings at the end of the output so the are more visible to the user). If we decided to go that route I would be tempted to move that logic here.

I think that an app like AppCode does not like ANSI, ever?

Why? If you don't know hot to interpret them they just look like any other stream of characters... no?

[alloy]

Why? If you don't know hot to interpret them they just look like any other stream of characters... no?

Yeah I have actually no clue, so never mind that :D

I’m on the fence about all of this. @kylef is right from a purist point of view of course.

[fabiopelosin]

I'm generally on the purist side on this things, but is really too and edge case for me.