Shouldn't parameter names be singular? Like nouns?


in process of re-working hastily-built ad-related functions , hoping improve compliance naming standards, revisited discussion:

    http://social.technet.microsoft.com/forums/en-us/winserverpowershell/thread/e81f335c-bf84-4ff5-84e6-d35ebf902f96

i had @ of active directory cmdlets, , see few of them include 'properties' parameter. makes sense, expect vast majority of ad queries looking more single property.

but isn't @ odds standard? none of suggested parameter names listed here:

    http://technet.microsoft.com/en-us/library/ee156811.aspx#emaa

are given plurals. select-object , format-* cmdlets have singular 'property' parameter, thought passed list of properties of interest.

so others think? ad cmdlets kind of erode standards of language? or there specific reason why appropriate? other comments?

 

no, many parameters (if not all) in singular.  consider get-childitem -path.  accept array of paths.

wait-job -job accept array of job references, , wait until complete (and).  there many other parameters accept list (array) singular.


grant ward, a.k.a. bigteddy

what's new in powershell 3.0 (technet wiki)

network live audit - powershell script


Windows Server  >  Windows PowerShell



Comments

Popular posts from this blog

Motherboard replacement

Remote Desktop App - Error 0x207 or 0x607

AD Replication Failure Between Server 2008 R2 and Server 2003 - LDAP bind failed with error 8341