Interactive runner that walks a Technique#103
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Introduces an interactive runner that walks a Technique, prompts the user with the details of the next step, takes their input, then records the result.
This branch adds technique run and technique resume to the command-line interface. The run subcommand reads a Technique document as parameter and starts presenting its steps. the resume subcommand resumes an interrupted run, taking a "run id" parameter to do so. This functionality is carried out in a new top-level
runner::module, with anevaluate()effectively taking an Operation and an Environment and evaluating it to a Value.The Value type is now defined in a new top-level
value::module, following the naming convention originally established in Technique v0.This lands an initial local state store for holding PFFTT files, written in .store/ in the present directory. These are named for the Technique document being executed and include basic information recording when each step is completed.
Branch also addresses a few corner cases that emerged while improving test coverage.