psusecompatibleSyntax goes a bit too far.

[jhoneill]

Not sure if something has changed but I've noticed this recently, and it the hadn't registered before

Summary of the new feature

I'm seeing this
The constructor syntax '[type]::new()' is not available by default in PowerShell versions 3,4
I got the same with class We're trying to get people to move on from Windows PowerShell 5, but that has been around for 8 yeas or so and it might be time to review the pre-PowerShell 5 features people are told to avoid

Proposed technical implementation details (optional)

Drop checks for PowerShell 3 compatibility.

What is the latest version of PSScriptAnalyzer at the point of writing
1.22.0

[iRon7]

It might also be considered to link this type of rules to the #Requires -Version x.x statement.

Originally posted by @iRon7 in #2046 (comment)

[jhoneill]

It might also be considered to link this type of rules to the #Requires -Version x.x statement.

Originally posted by @iRon7 in #2046 (comment)

YES . If the solution were "Put a requires statement in if your code uses feature only in XX" (which only appeared if there was no such statement) that would be ideal.