You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a nullable boolean with an option of type CommandOptionType.SingleOrNoValue, the argument value isn't binded. It only works if the property isn't nullable.
To Reproduce
Using version 4.0.2 of the library. To reproduce, add a property with a nullable boolean
Describe the bug
When using a nullable boolean with an option of type
CommandOptionType.SingleOrNoValue
, the argument value isn't binded. It only works if the property isn't nullable.To Reproduce
Using version 4.0.2 of the library. To reproduce, add a property with a nullable boolean
Execute with the argument
--install-proxy
or--install-proxy=true
or--install-proxy=false
.The
InstallProperty
value will still be set to null.The output
Expected behavior
I would expect the argument value to be binded to the property value.
Screenshots
The text was updated successfully, but these errors were encountered: