Add interactive GUI PROMPT for Script session runs - #618
Merged
Merged
Conversation
Visible script runs emit a prompt request to the Reports Script view, block until the user answers or cancels, and keep env/default fallbacks for noninteractive and Silent mode.
Unit tests that mount Reports Script without event mocks must not throw or leave unhandled rejections when listen is unavailable.
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.
Summary
OPEN_DIFF_SCRIPT_PROMPT_*and Silent-mode defaults keep noninteractive behavior; unit tests cover handler answer and cancel.Test plan
cargo test -p script-core promptcargo test -p open-diff-app run_script