feat: Add ConvertTo-InvokeParameterString and test

InvokeHelperTest/public/Invoke-MyCommand.test.ps1

@@ -76,4 +76,37 @@
     Assert-AreEqual -Expected 'fakeName' -Presented $result.login
     Assert-AreEqual -Expected 6666666 -Presented $result.id
 
+}
+
+function InvokeHelperTest_Invoke_MyCommand_WithDoubleQuotes {
+    [CmdletBinding()]
+    param()
+
+    $str = 'Hello "world"'
+    $command = 'echo "{string}"'
+
+    ## Wrong call with no parameter formatting
+
+    # Arrange
+    $param = @{
+        string= $str
+    }
+    # Act
+    $result = Invoke-MyCommand -Command $command -Parameters $param
+
+    # Assert
+    Assert-AreNotEqual -Expected $str -Presented $result
+
+    # Correct call with parameter formatting
+
+    # Arrange
+    $param = @{
+        string= $str | ConvertTo-InvokeParameterString
+    }
+
+    # Act
+    $result = Invoke-MyCommand -Command $command -Parameters $param
+
+    # Assert
+    Assert-AreEqual -Expected $str -Presented $result
 }

public/Format-InvokeParameterString.ps1

@@ -0,0 +1,20 @@
+
+# Invoke command use powershell calls to manage the dependencies
+# if a string contains double quotes, it will fail as it will confuse the string content with parameter values
+# so we need to escape the double quotes in the string to ensure the quotes that are part of the string value and not parameter boundaries
+
+function ConvertTo-InvokeParameterString {
+    param (
+        [Parameter(ValueFromPipeline, Position = 0)][string]$InputString
+    )
+
+    process{
+
+        if ([string]::IsNullOrEmpty($InputString)) {
+            return $InputString
+        }
+
+        $OutputString = $InputString -replace '"', '""'
+        return $OutputString
+    }
+} Export-ModuleMember -Function ConvertTo-InvokeParameterString