UseColourInput
Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/config/colour.ts:10
Everything the colour decision depends on. See resolveUseColour.
Properties
Section titled “Properties”explicitUseColour?
Section titled “explicitUseColour?”
optionalexplicitUseColour?:boolean
Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/config/colour.ts:24
useColour as the user actually wrote it — read from the RAW config, BEFORE DEFAULT_CONFIG
is merged in. undefined means the user set nothing, which is what rung 3 tests for; after the
default merge an explicit true is indistinguishable from the default true, so this value
must be captured pre-merge or the rung collapses.
forceColor?
Section titled “forceColor?”
optionalforceColor?:string
Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/config/colour.ts:15
Raw FORCE_COLOR environment value; undefined when the variable is not set at all.
The empty string is a SET value (FORCE_COLOR= on the command line) and means colour on.
noColor?
Section titled “noColor?”
optionalnoColor?:string
Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/config/colour.ts:17
Raw NO_COLOR environment value; undefined when the variable is not set at all.
stdoutIsTTY
Section titled “stdoutIsTTY”stdoutIsTTY:
boolean
Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/config/colour.ts:26
Whether stdout is a terminal. Rung 4’s auto-detection; stdout, not stdin.