Write-PSFMessage [switch] input handling for -EnableException

[mattcargile]

Looks like an issue with pwsh 7.4.6 binder. Just thought I would point it out I guess because Stop-PSFFunction doesn't have this issue. Maybe creating a new type would help and not be breaking? I guess I can also just switch to using Stop-PSFFunction instead.

PSF Demo

& { param([switch]$a ) Write-PSFMessage 'hello' -EnableException $a } 

Generic Demo

Add-Type '
using System.Management.Automation;

[Cmdlet("Test", "Command")]
public sealed class TestCommand : PSCmdlet
{
    [Parameter]
    public bool EnableException;
}' -PassThru | Import-Module -Assembly { $_.Assembly }
Test-Command -EnableException ([switch]::new($false))

PSF Working Demo

& { param([switch]$a ) Stop-PSFFunction -Message 'hello' -EnableException $a } 

[FriedrichWeinmann]

Heya, thanks for bringing this up!
Looks like I forgot to apply my fix to Write-PSFMessage, fixing that in the next release.

It's part of the type-transformation in Parameter binding being a bit inconsistent here - functions (such as Stop-PSFFunction) don't have the issue, Cmdlets however do. The implementation workaround (which I already added to Invoke-PSFProtectedCommand, but not to Write-PSFMessage, apparently) is a type transformation attribute:

$source = @'
using System.Management.Automation;
using PSFramework.Utility;
using System;

[Cmdlet("Test", "Command")]
public sealed class TestCommand : PSCmdlet
{
    [Parameter]
    [TypeTransformation(typeof(Boolean))]
    public bool EnableException;
}
'@
$ref = [appdomain]::CurrentDomain.GetAssemblies() | Where-Object Location
Add-Type $source -ReferencedAssemblies $ref -PassThru -IgnoreWarnings -WarningAction Ignore | Import-Module -Assembly { $_.Assembly }
Test-Command -EnableException ([switch]::new($false))

This assumes you have PSFramework already imported.

Will be fixed in the next release :)