[cli] Move output command state out of CliContext #426
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes it a lot easier to integrate new output commands into the CLI. The goal is to have the controller treat all output commands the same by operating on the result of the processing pipeline. For dependent jobs, they can still use the shared context to communicate results. This has a few benefits:
split-video
twice to generate output videos with different parameters--verbosity debug
This should also help reduce the friction to adding new output formats, supporting #156, #323, and #388. As part of this change, some log statements will now be emitted later when a command is actually running. Previously, some commands would emit things like the location of saved files when processing the command-line arguments, rather than when the sub-command was about to run.