-
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add stacktrace context to inline code #65
Conversation
Instructions and example for changelogPlease add an entry to Example: ## Unreleased
- add stacktrace context to inline code ([#65](https://github.com/getsentry/sentry-powershell/pull/65)) If none of the above apply, you can opt out of this check by adding |
Describe 'Out-Sentry captures expected stack traces for PowerShell.Create()' { | ||
BeforeEach { | ||
Push-Location "$PSScriptRoot/.." | ||
$expected = @( |
Check warning
Code scanning / PSScriptAnalyzer
The variable 'expected' is assigned but never used. Warning test
This adds source context for frames present in the original script code, e.g. by running
pwsh -c '{& ... }'
. It should also work for situations when the script is launched directly without a ps1 file, e.g. from Azure automation workers