Added support for the empty arguments passed to the command #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for explicitly passing empty string values to PowerShell command arguments when configured to allow them. Previously, empty string arguments were filtered out and not included in generated commands. This enhancement provides more flexibility for PowerShell cmdlets that distinguish between omitted parameters and explicitly empty parameters.
The need has originated from the ability to remove the value set for certain properties this is the way to do it via Powershell.
Test coverage has been added to cover the addition.
Change is a nonbreaking change ensuring existing implementation will not break upon upgrade.
Example:
Currently generating:
Set-Content -Path './test.txt' -Filter '*.txt'
Desired output:
Set-Content -Path './test.txt' -Value '' -Filter '*.txt'
This is archived by marking argument
Filter
asempty
in the commend definition.