Repository navigation
Let hosts run a specification's slice isolation themselves - #1061
Merged
Merged
Conversation
Expose Runs, RunningReactions and RunningCaptures so an executor outside Screenplay, such as Stage's, can narrow its reactions, captures and publications to the isolated slice.
Contributor
Author
|
Corpus impact: none - only widens host API visibility; the language and its semantics are unchanged (the semantic change is tracked in Cratis/AI#926 from #1060). |
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.
Added
SemanticExecutionPlan.Runs,RunningReactionsandRunningCapturesare public, so a host with its own specification executor can run only the isolated slice's reactions, captures and publications, the way Screenplay's runner does.