-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
Add support for ansi
colors and add .ansi256ToAnsi()
, .rgbToAnsi()
and .hexToAnsi()
#71
Conversation
…()` and `.hexToAnsi()` Signed-off-by: Richie Bendall <[email protected]>
@Qix- LGTY? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few nits
Co-authored-by: Qix <[email protected]>
Co-authored-by: Qix <[email protected]>
Co-authored-by: Qix <[email protected]>
The CI is yet to have cached a version of |
Can we get some tests for Otherwise, LGTM. Thanks for the heads up about the failing test. |
Since this function is being added to |
I disagree, but okay. Chalk does not rely on color convert any longer so their testing concerns no longer overlap. If you're going to vendor code, you should include automated tests in the destination codebase, IMO. |
If it's a direct copy-paste from the original codebase that is already tested, then IMO unit tests aren't nessessary. Now would be the time to add the short-circut to |
Sorry, I missed the comment about tests. I agree we should have some tests here too. |
chalk/chalk#433 (comment)