fix(tui): make playbook templates keyboard accessible - #1249
Merged
Conversation
Contributor
Author
Contributor
Author
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.
Fixes #1099.
Summary
↑/↓ or C-p/C-n select · Enter applykeyboard affordance to the empty Playbook template listVerification
cargo check -p construct-clicargo test -p construct-cli playbook_empty_template -- --nocapture(2 passed)cargo test -p construct-cli playbook_empty_placeholder -- --nocapture(9 passed)cargo buildcargo test -p construct-cli: 1,395 passed;color::tests::truecolor_backend_still_emits_rgbfails identically on untouchedmainin this environmentDemo
After-only recording captured from the worktree binary. It opens an empty Playbook, shows descriptions + key hint, focuses Goal with C-n, and applies it with Enter.