Dynamic user interface#110
Merged
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
1 participant
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.
There are now two modes for running a Technique, "interactive" and "automatic". This allows us to differentiate between the program being used in a script or having its output redirected, and a fully interactive interaction with the user.
Upgrade the console output from the previous line oriented buffered output to a more dynamic user interface for "interactive" mode, leveraging the crossterm crate to handle raw keyboard input and line redrawing.
By default pressing <Enter> will result in the step being marked as Done; in cases where there are preset responses they are presented as choices.
Pressing <Esc> toggles a modal switch to presenting a menu of options to Skip the step, mark it as Failed (and enter a reason why), or to Quit. The latter records a new
Stopevent in the PFFTT log, allowing us to later differentiate between someone stopping or pausing the procedure run and a crash (which would lack the event).This series of PRs marks a significant capability improvement and also some semantic changes to the verbs in PFFTT and so we've bumped the major version to
0.6.