Open ghost opened 5 years ago
@alexbuzzbee thanks for reporting this bug, and taking the time to do some de-bugging...both of your proposed solutions seem valid, although we are undertaking a major re-work of PowerShellGet right now so I cannot promise we will have bandwidth to address this in the near future (although we do accept PRs 😄 )...thanks!
... although we are undertaking a major re-work of PowerShellGet right now ...
@SydneyhSmith can you please provide more information on this?
Yes--the RFC is here: https://github.com/PowerShell/PowerShell-RFC/pull/185 We are targeting a public preview for this module by the end of this year.
@SydneyhSmith Ok, thank you!
Steps to reproduce
Expected behavior
Module published.
Actual behavior
Environment data
Additional information
My debugging attempts tracked the issue down to this line in
New-NugetPackage
:This casts an array (
$ArgumentList
) to a string, assuming that it will be joined with spaces. This is only true if$OFS
is set to" "
, which, while currently the default, is not guaranteed.This bug exists in other functions called during the publishing process, but
New-NugetPackage
is the first one to trigger it.Proposed solution
One of:
-join
.$processStartInfo.Arguments
to a string with appropriate interpolations.