-
Notifications
You must be signed in to change notification settings - Fork 394
Improvements to Positional Parameters rule #301
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
Comments
Here is the Pull request: |
So I have 1.1.1 which was released on Nov 3rd. But I'm getting PSAvoidUsingPositionalParameters on this line:
This is only using one positional parameter. What gives? FWIW, if this rule only fired on the use of three or more positional parameters, I think it should be a warning as it does impact the readability of the script. Also, by allowing two positional parameters, I'm not sure you need a whitelist - IMO. |
Hi Rob, this is probably a bug. We are looking into it. |
Closed with #406 |
Need to make the following changes to make the rule more usable:
The text was updated successfully, but these errors were encountered: