Skip to content

#353 - cleverage:process:execute: reliable output options - #354

Open
njoubert-cleverage wants to merge 1 commit into
mainfrom
353
Open

njoubert-cleverage wants to merge 1 commit into
mainfrom
353

Conversation

@njoubert-cleverage

Copy link
Copy Markdown
Member

Description

Fixes #353.

  • The process codes and the output format are checked before any process is executed (new checkOutputFormat(), explicit message for dump without symfony/var-dumper, dump only to STDOUT).
  • With --output-format, the output is printed to STDOUT whatever the verbosity (it required -vv).
  • A non-array output that cannot be stored in the --output file as JSON stream is reported on the error output (it was silently lost, also for process_launcher with json_buffering).
  • Documentation of the options (01-quick_start.md); new ExecuteProcessCommandTest (the command had no test, Tasks services should not be public #114).

Requirements

  • Documentation updates
    • Reference
    • Changelog
  • Unit tests

Breaking changes

Behaviour change: -t dump / -t json-stream to STDOUT print the output without -vv.

🤖 Generated with Claude Code

…put format before any execution, print the output whatever the verbosity, report a non-array output that cannot be stored. Update documentation, add tests.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.

cleverage:process:execute: output options silently ignored, invalid options detected after the execution

1 participant