Joshua Yoes

I've added [failing tests](https://github.com/infinitered/gluegun/blob/0ac61621dd2d5ac1d9017b4e7cb0d67c0bc9e168/src/toolbox/parameter-tools.test.ts) to demonstrate desired behavior, you can see [a sample of those failed test runs here](https://dev.azure.com/infinitered/gluegun/_build/results?buildId=889&view=logs&j=12f1170f-54f2-53f3-20dd-22fc7dff55f9&t=bd05475d-acb5-5619-3ccb-c46842dbc997&l=188)

Only problem I see is that this would definitely be a breaking change in my eyes

It also may be better to take a [PR like this](https://github.com/infinitered/gluegun/pull/464), where we could provide the `yargs-parser` object optionally, and then allow for opting into coalescing options

Got some input from Jamon. Gluegun already doesn't have great type-safety guarantees on command parsing, so this quality of life improvement would be worth a potentially breaking change

 https://dev.azure.com/infinitered/gluegun/_build?view=runs I think something changed about ts-node or typescript dependency between now and May. I don't think these changes are causing this...

There has been a lot of changes since this issue last had activity. This is going to be closed for now, but please re-open if this still needs attention.

There has been a lot of changes since this issue last had activity. This is going to be closed for now, but please re-open if this still needs attention.

There has been a lot of changes since this issue last had activity. We have release a new major version of Ignite, codenamed Maverick. This is going to be closed...

There has been a lot of changes since this issue last had activity. This is going to be closed for now, but please re-open if this still needs attention.

There has been a lot of changes since this issue last had activity. This is going to be closed for now, but please re-open if this still needs attention.