iRon7

I did a number of improvements to my prototype but in fact the scope of the rule could be even more wider and might also applied to (incorrect) statements like:...

You might also consider to link this type of rules to the [`#Requires -Version x.x`](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_requires#-version-nn) statement. (In case it doesn't exist in the concerned script: simply suppress the warning.)

> Agree with it, feel free to contribute a rule for it :-) Might that be a PowerShell based rule? (FYI: I don't have enough C# known to write something...

@DrSkillIssue, Thank you for picking this up! I was about to write a rule in PowerShell but wasn't ably to do more than just some preparation before my holidays last...

Some thought should be put in headerless csv files (such as the example I referred to [Sort-Object and Integers](https://stackoverflow.com/q/15040460/1701026)): The `-Header` parameters could support the same format as the purposed...

Please either mark this issue with something like Resolution-Declined or put it on a kind of wishlist "[*Issue we would like to prioritize, but we can't commit we will get...

Please either mark this issue with something like Resolution-Declined or put it on a kind of wishlist "[*Issue we would like to prioritize, but we can't commit we will get...

Please either mark this issue with something like Resolution-Declined or put it on a kind of wishlist "[*Issue we would like to prioritize, but we can't commit we will get...

Although I think that calculated properties are rather verbose (see also: [#11866 Simplified calculated property syntax](https://github.com/PowerShell/PowerShell/issues/11866)), a general `-Property` parameter might fit here. wishful thinking: ```PowerShell $UserList = Import-Csv -Property...

@SeeminglyScience, > There's already an option to ignore it I changed the title and removed Completely remove the unapproved verbs warning or in the propose. Meaning that propose is to...