-
Notifications
You must be signed in to change notification settings - Fork 12.9k
Revisions for the new --help #44800
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
Revisions for the new --help #44800
Conversation
What's the before/after look like? |
There is 3 ways blue can show:
|
@typescript-bot pack this |
Heya @DanielRosenwasser, I've started to run the tarball bundle task on this PR at b8015ef. You can monitor the build here. |
For something with a pure white background (e.g. the default MacOS terminal theme) how does that look? On a white background, I'm getting a contrast ratio of 3.53 which is still fairly low. Seems like if bright blue is this on CMD and this is bright blue on PowerShell that might work, though it's a bit off from brand colors. |
Hey @DanielRosenwasser, I've packed this into an installable tgz. You can install it for testing by referencing it in your
and then running There is also a playground for this build and an npm module you can use via |
hahaha, well, I guess I need to get a windows VM up and running 🍡 |
This is your big chance to tell us how you feel about Windows 11. 😅 |
What are your thoughts on just using a brighter white if 256 color isn't available? |
I'm not offended, will switch it now |
@typescript-bot pack this |
Heya @DanielRosenwasser, I've started to run the tarball bundle task on this PR at 2c5a07d. You can monitor the build here. |
Hey @DanielRosenwasser, I've packed this into an installable tgz. You can install it for testing by referencing it in your
and then running There is also a playground for this build and an npm module you can use via |
@@ -90,32 +90,53 @@ namespace ts { | |||
} | |||
|
|||
function createColors(sys: System) { | |||
const showColors = defaultIsPretty(sys); | |||
const showColors = defaultIsPretty(sys) || !!sys.getEnvironmentVariable("NO_COLOR"); |
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.
This looks wrong. Shouldn't it be defaultIsPretty(sys) && !sys.getEnvironmentVariable("NO_COLOR")
? If NO_COLOR
exists, then we shouldn't print color... as is, if NO_COLOR
is set, then tsc will write with colors even if it is not printing to a terminal.
(There's also the consideration that we should be checking for existence, not non-emptyness, but that's less important)
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.
Coming back to this - I think the environment check belongs in the defaultIsPretty
function... but maybe I don't understand that yet.
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.
Thanks, yeah I was avoiding making more drastic changes by adding NO_COLOR support everywhere (somewhat making this bug-fix a feature) by moving it into defaultIsPretty
- running the tests now too see how that changes the test suite.
(edit: looks like no changes)
I've switched to have |
@typescript-bot pack this |
Heya @DanielRosenwasser, I've started to run the tarball bundle task on this PR at c350c39. You can monitor the build here. |
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.
It would be nice to try this out first - I won't block on that though.
@@ -14,5 +14,14 @@ namespace ts { | |||
fs: () => loadProjectFromFiles({}), | |||
commandLineArgs: [], | |||
}); | |||
|
|||
verifyTsc({ |
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.
Seems like these tests generate a .js
file - would be awesome if we could change that though.
Hey @DanielRosenwasser, I've packed this into an installable tgz. You can install it for testing by referencing it in your
and then running There is also a playground for this build and an npm module you can use via |
Co-authored-by: Daniel Rosenwasser <[email protected]>
Requests merged, I'm going to get this in so that it doesn't get overlooked before the RC |
Fixes #44798