-
Notifications
You must be signed in to change notification settings - Fork 49
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-PSRuleHelp search into the current directory by default #197
Comments
@LaurentDardenne Yeah, so The reasoning for this was that modules are more likely to have markdown help created for them then standalone rules.
This this behaviour may be confusing since, most of the other PSRule cmdlets operate on the current working path first. However i'm interested in your feedback to improve this in the future. |
According to the documentation:
If one is already in the directory of a script of a rule, I think that if Path is not informed one can first search the help file in the current directory before displaying an error s' he does not exist. |
The cmdlet Get-PSRuleHelp must search into the current directory if the 'Path' parameter has no argument :
One rule file exist into the current directory, but Get-PSRuleHelp do not read it :
When I specify the 'Path' parameter with a relative path, it finds the help file
That said, research in the current path can often be problematic with Powershell :
The text was updated successfully, but these errors were encountered: