Skip to content
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

Errors from incorrect settings files are not actionable #1053

Closed
LeeHolmes opened this issue Aug 3, 2018 · 1 comment · Fixed by #1263
Closed

Errors from incorrect settings files are not actionable #1053

LeeHolmes opened this issue Aug 3, 2018 · 1 comment · Fixed by #1263

Comments

@LeeHolmes
Copy link

The errors from Script Analyzer when there is an error in a setting file are not actionable. There is nothing in $error, $stacktrace, etc. This error should be returned as a terminating error, not a warning - and should include the reason that the settings file was broken.

12 [C:\Users\leeholm]
>> '@{ Blah = $true }' > c:\temp\settings.psd1

13 [C:\Users\leeholm]
>> Invoke-ScriptAnalyzer -Path C:\temp\test.ps1 -Settings c:\temp\settings.psd1
WARNING: Cannot parse settings. Will abort the invocation.
@bergmeister
Copy link
Collaborator

Yes, I can confirm that and have run into this issue as well in the past.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants