--set command doesn't work when only passing one of them

[davehibshman]

1. Passing a single --set option: winser -i -s --set "Application C:\path\of\some\kind.exe" returns with error message: Set operation failed (e)

2. Passing multiple set options: winser -i -s --set "Application C:\path\of\some\kind.exe" --set "AppParameters start" works fine.

Watching typeof options.set in the debugger in both circumstances it appears when passing a single --set argument options.set type is 'string', however when passing more than one it is of type 'object', specifically upon further inspection, it is an array as expected.

Line #313 in the current file async.each(options.set, appears to expect an array in all cases and thus fails for the first case listed above.

I am not sure if this is how stdio.getopts is intended to work or not, but I think it's a bug here none the less. I'll submit a pull request if author doesn't address this. There may be other areas of the code where this is a problem, probably any args marked as expecting mutiple.

Note if you need the current code to work with one -set argument you can pass a second --set option that is just a single space, or anything really, except nothing or empty string. You will get an error message stating 'Set operation failed ( )' for the second arg if it isn't a valid arg, but the first one will work as expected.

Windows 8.1 Enterprise
node v0.12.0
npm v2.5.1
winser v^1.0.2

[kanreisa]

👍

[Codesleuth]

We've opened a pull request with this fix.