Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix non standard ANSI colors #2164

Closed
wants to merge 1 commit into from
Closed

Conversation

jtangelder
Copy link

Replaces the non standard 90-97 color range to their standard 30-37 range. This should fix colors from not showing up, like on Travis.

@danielstjules
Copy link
Contributor

We've had issues with changing colors in the past, so this will prob need a bit of time to review. That said, I haven't had any problems using those values with a toy project a couple years ago https://github.com/danielstjules/pho/blob/master/src/Console/ConsoleFormatter.php#L22-L35

@danielstjules
Copy link
Contributor

Since we couldn't upgrade to chalk, we can prob copy values from ansi-styles: https://github.com/chalk/ansi-styles/blob/master/index.js#L27-L60 Note that we can't use ansi-styles directly since it would break compatibility with older version of NPM due to its use of tilde in package.json

@boneskull
Copy link
Contributor

@jtangelder can you please rebase this onto master? I want to see how the phantom test(s) are affected.

Replaces the non standard 90-97 color range to their standard 30-37 range. This should fix colors from not showing up, like on Travis.
@jtangelder
Copy link
Author

Rebased!

@boneskull
Copy link
Contributor

@jtangelder Thanks!

Someone (maybe me) should pull down this PR and see what mochify's output looks like. @mantoni are you interested in doing this?

@mantoni
Copy link
Contributor

mantoni commented Jun 17, 2016

Sure. Looks like my computer is offline for the day due to some technical issues with my provider. Hopefully I'm able to check tomorrow.

@mantoni
Copy link
Contributor

mantoni commented Jun 18, 2016

Looking good here. I can't see any difference.

bildschirmfoto 2016-06-18 um 12 33 22

@boneskull
Copy link
Contributor

basically floored that nyan works w/ mochify

@boneskull
Copy link
Contributor

So this solves #1200, apparently, but I can't reproduce a problem, so I'm having trouble understanding how this actually changes anything. Help?

@boneskull boneskull added type: bug a defect, confirmed by a maintainer unconfirmed status: waiting for author waiting on response from OP - more information needed labels Jul 1, 2016
@boneskull boneskull changed the title Fix non standard ANSI colors Fix non standard ANSI colors; closes #1200 Jul 1, 2016
@boneskull boneskull added this to the 2.6.0 milestone Jul 1, 2016
@r-tanner-f
Copy link

r-tanner-f commented Jul 1, 2016

Hmm, this doesn't seem to fix #1200 when using iTerm and the official Solarized theme. I'm still seeing 'pass' text as the background color.

Starting to look like a problem with Solarized though. It's using bright black as the background (base03 is the background for dark theme), which is the same as the 'pass' text that Mocha is using. I'd tend to assume that the value 'black' is going to be the background, and 'bright black' would show up on black (though maybe not well). Just a thought.

@boneskull
Copy link
Contributor

@jtangelder Can you show an example of where Travis fails to show colors without this change?

@boneskull boneskull removed type: bug a defect, confirmed by a maintainer unconfirmed labels Jul 1, 2016
@boneskull boneskull changed the title Fix non standard ANSI colors; closes #1200 Fix non standard ANSI colors Jul 1, 2016
@boneskull boneskull modified the milestones: v3.0.0, 2.6.0 Jul 2, 2016
@jtangelder
Copy link
Author

Can't reproduce anymore. But I think it still is a good idea to use the standard colors instead of the non-standard alternatives.

@boneskull
Copy link
Contributor

In general I think this is a good idea. I'm not sure if this got merged in the shuffle. If anyone wants to double-check or look at the changelog, then I'll close it if it was.

@boneskull
Copy link
Contributor

Closing for inactivity; unclear if issue reproducible

@boneskull boneskull closed this Aug 28, 2016
@jtangelder jtangelder deleted the patch-1 branch October 1, 2016 09:06
@boneskull boneskull removed the status: waiting for author waiting on response from OP - more information needed label Dec 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants