-
Notifications
You must be signed in to change notification settings - Fork 386
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
Question about PSUseCompatibleSyntax #1384
Comments
It could be wrong. I was under the impression that that feature was added later, but if testing shows it works in PS 3, we should correct that. It should be fairly simple to take out if you'd like to open a PR: PSScriptAnalyzer/Rules/CompatibilityRules/UseCompatibleSyntax.cs Lines 210 to 278 in 6a5d2ff
|
Thanks. |
@LaurentDardenne is the rule incorrect? If so, we should keep this issue open to track the need to fix it |
Almost incorrect ;-) |
I use this script with Powershell v3 ( Citrix farm with W 2008)
I run PSSA version 1.8.3 with this settings :
When I run PSSA under PS 5.v0 I get this result :
But when I read my logs, the rule message 'The dynamic member invocation syntax' seems incorrect and do not match the specifications in the 'Windows PowerShell Language Specification Version 3.0' file, chapter 7.1.2 Member access :
The following Error (see $Method.$method() ), is saved by Export-CliXml:
Moreover the rule should be of severity 'Error' when I try to know if my code is compatible with Powershell v3, unless I did not understand the use and the behavior of this rule.
Why indicate that some syntax is problematic when it is not?
The text was updated successfully, but these errors were encountered: