Display Options

Control how Dyngle displays operation steps during execution.

The --display Option

The run command supports a --display option to control step visibility:

dyngle run <operation> --display <mode>

Available Modes

steps (default)

Show each step before executing it:

dyngle run build --display steps

Output:

$ npm install
[npm install output here...]

$ npm run build
[build output here...]

none

Suppress step display for cleaner output:

dyngle run build --display none

Output:

[npm install output here...]
[build output here...]

When to Use Each Mode

Use `steps` mode when:

Debugging operations - See exactly what commands are being executed
Learning - Understand what's happening during execution
Development - Verify that template substitution is working correctly
Interactive use - Get visual confirmation of progress

Use `none` mode when:

Scripting - Cleaner output for parsing or processing
Production workflows - Reduce noise in logs
Return value focused - When you only care about the final result
Automated systems - CI/CD environments where step display is unnecessary

Examples

Development workflow with step display

dyngle run test --display steps

Useful for seeing exactly what test commands are being run.

Production deployment with clean output

dyngle run deploy --display none

Keeps deployment logs focused on command output without displaying each step.

Combining with return values

When an operation has a return value, none mode is particularly useful:

dyngle:
  operations:
    get-version:
      return: version
      steps:
        - cat package.json => pkg
        - pkg -> jq -r '.version' => version

With steps mode:

$ dyngle run get-version --display steps

Output:

$ cat package.json => pkg
$ pkg -> jq -r '.version' => version
1.2.3

With none mode:

$ dyngle run get-version --display none

Output:

1.2.3

Interaction with Return Values

Display options work with the script mode vs function mode behavior:

Script mode (no return:): Step display controlled by --display option
Function mode (with return:): Stdout already suppressed; --display controls step visibility

See Return Values for more details on script vs function mode.

stderr is Always Displayed

Regardless of the --display setting, stderr is always shown. This ensures error messages and warnings remain visible:

dyngle run failing-operation --display none

Will still show error output from commands, even though steps are hidden.

Default Behavior

If you don't specify --display, it defaults to steps mode for maximum visibility during development and debugging.