Runnable Scripts passes in $args for pwsh scripts causing errors if the script uses params

[a-m-brewer]

I have created a pwsh script with params e.g.

param(
    [Parameter(Mandatory=$false)]
    [string]$InterfaceName = "Switch Name",

    [Parameter(Mandatory=$false)]
    [string]$SSHConfigName = "config_example",

    [Parameter()]
    [Switch]$Backup
)

I have given it the following execution types

I know that "Runnable scripts" have no way to enter arguments so in my script I have left fallbacks with my most common configuration. With the idea that if I need something more advanced I will start a shell session and run the script as a "Shell session script"

However, when I run the script I get the following

Is this a bug or is there a better way of handling this scenario?

Also I know this is more of a feature request, but would it be possible to have some sort of way to define common argument configurations so you could select "Runnable A" > "Argument Set B".

[crschnick]

I guess that is an issue with Powershell specifically due to how it handles arguments. Is there some way to pass through all arguments to a sub script, even named ones?

[a-m-brewer]

You can pass arguments without names e.g. .\script.ps1 "a" "b" "c" and it will map it in the order it's defined. Or you can use named ones like .\script.ps1 -B "b" and it would only pass B.

You can also define hashtables that map to arguments e.g.

param (
    [string]$FirstName = "John",

    [string]$LastName = "Doe"
)

Write-Host "Hello, $FirstName $LastName!"

Then use it as follows

$params = @{ FirstName = "Foo"; LastName = "Bar" }
.\test.ps1 @params
Hello, Foo Bar!

$params = @{ FirstName = "Foo"; }
.\test.ps1 @params
Hello, Foo Doe!

$params = @{} 
.\test.ps1 @params
Hello, John Doe!

Note that $args is a reserved PowerShell variable which is just an array without names of the parameters and will pass it like .\script.ps1 "a" "b" "c"

Does this help?

[crschnick]

Thanks, that clears it up for me. I implemented a quick fix in https://github.com/xpipe-io/xpipe-ptb by just removing the $args when it is not needed. So that should work at least. I will look how I can properly handle these params