not using [parameter()] on some parameters in a PowerShell advanced function

Question

If you are doing advanced functions and have the parameters decorated [parameter()], would there be any reason to NOT decorate a parameter with [Parameter()] . I've seen this a few times and don't know whether its just a case of laziness, oversight, or purposeful design.

Keith Hill · Accepted Answer · 2011-03-11 17:01:15Z

4

Laziness I think but to be fair, it isn't needed if you aren't using any special parameter attibutes like Mandatory, Position, etc. As long is one parameter is marked [Parameter(...)] or the param block is marked [CmdletBinding(...)] PowerShell will interpret that function as an advanced function. OTOH there is no harm in adding the empty [Parameter()] to parameters.

answered Mar 11, 2011 at 17:01

Keith Hill

204k44 gold badges370 silver badges377 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

klumsy Over a year ago

Yeah i think though if you are using it on any, its probably best to be consistent, especially if you are doing some parametersets IMO.

Keith Hill Over a year ago

FWIW, that is what I usually do.

JasonMArcher Over a year ago

It is probably best to put them on all parameters... but I do tend to leave them off of switches.

Collectives™ on Stack Overflow

not using [parameter()] on some parameters in a PowerShell advanced function

1 Answer 1

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related