Session state hints #1169
Merged
Session state hints #1169
Conversation
This file contains 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.
Add debugging output that captures all session states and describes them by which module they come from or where we captured them. Based on the output it is then easy to see in which scope the code is invoked and makes debugging problems easy. It also shows how deep in the session state we are running. So given a scripblock
$sb = {}invoking it like this&$sbwould report 0 scopes deep, and&{ &{ &{ &$sb } } }would report 3 scopes deep. The output is disabled by default, and can be enabled by providing@{ Experimental = $true; ShowScopeHints = $true }Pester option toInvoke-Pester.