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

Get-DSCResource to show when there are syntax errors. #46

Open
bagajjal opened this issue May 21, 2021 · 0 comments
Open

Get-DSCResource to show when there are syntax errors. #46

bagajjal opened this issue May 21, 2021 · 0 comments

Comments

@bagajjal
Copy link
Collaborator

Current behavior -
Get-DSCResource shows a generic message " The term {0} is not found as a resource" when there is a syntax error in the DSC resource (.psm1).

Feature request -
In case of syntax errors, Get-DSCResource should show the actual syntax error message.

Given Get-DscResource can be called without any arguments, this might clutter the console output if there are way many modules with syntax errors in $env:PSModulePath. It's good idea to surface the underlying syntax error message only when user calls Get-DscResource -Module

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

No branches or pull requests

1 participant