Splatting is a really great feature in PowerShell that lets you take a
[hashtable] of parameters and call a function or cmdlet with the hash instead of having to type out every parameter name and value. It seems natural then that if you’re writing a wrapper or proxy function, where your function takes the same or nearly the same parameters as the function you’re calling, you could use
$PSBoundParameters to do the heavy lifting (this special variable contains all of the parameter values passed into the function).
The problem comes when your proxy function has defaults for its optional parameters.
$PSBoundParameters only includes the values of parameters that were explicitly supplied by the caller. There is no such variable that contains the default values.
I’ve created a small code snippet which alleviates this. It finds the parameters of your script or function, then gets the actual current values (you can override the supplied parameter values), and puts them all in a
$MyInvocation.MyCommand.Parameters to get all of the parameter names, and then I’m using
Get-Variable to get the actual current value of it.
That means any default value of a parameter will be counted. It was also especially useful for me because I was doing additional checking and in some cases changing the values of the parameters. This method will see the new values, so the resulting hash will be “complete”.
I found that in some cases
Get-Variable threw an exception because it couldn’t find the variable. This was actually because of automatic parameters like
$Verbose which actually translate into
$VerbosePreference and the like, so these will not be included in the hash.
I also found that optional parameters which didn’t supply a default were being included in the hash. That’s the part where I check for
$val being null or empty. I also check to see if it’s included in
$PSBoundParameters and if not, it won’t be included.
This check is specifically for the case where you intentionally passed in a
$null or an empty string, so that they won’t erroneously be excluded.
Here’s a complete example with 2 functions.
Note that the proxy function here has an additional switch parameter called DoThing, and if that’s specified then we’re modifying the value of Mandatory3. Note that since the function we’re proxying doesn’t contain that parameter, we have to remove it from the hash before splatting.
The output of the above script is: