--no-ansi still outputs colour

Hi,

It looks like even for the cases that --no-ansi is used, [26m is printed in various places ;

1. On Scenario, Scenario Outline, Feature definitions ; e.g.

Feature·[26m: Tagging Enforcement·[26m  # /tmp/tmpoatbd3is/tags.feature·[26m 
    In order to keep track of resource ownership 
    As engineers 
    We'll enforce tagging on all resources·[26m 

1. At the end of each Scenario and Scenario steps ; e.g.

    Scenario·[26m: Ensure all resources have tags·[26m 
        Given I have resource that supports tags defined·[26m 
        Then it must contain tags·[26m 
        And its value must not be null·[26m 

1. On any assertions that are raised from the steps e.g.

Failure·[26m: tags property in module.something.aws_iam_role.pipeline_role resource matches with Null/None regex. It is set to None.·[26m 

1. On Example tables defined within Scenario Outlines ; e.g.

    Examples·[26m: 
        | tag_keys            | pattern             | 
        |·[26m Data Classification |·[26m ^PROTECT - PRIVATE$ |·[26m 
        |·[26m Data Residency      |·[26m ^EU$                |·[26m 
        |·[26m Compliance          |·[26m ^GDPR$              |·[26m 

This is an environment where TERM is not set ( e.g. AWS CodeBuild ) where any colour codes will not work.

[timofurrer]

@eerkunt I can reproduce your issue. It seems to be a problem with nested colors in colorful.

[timofurrer]

Awesome! Thanks for verifying. I’ll release colorful asap. 🎉