Skip to content

Conversation

@billbogaiv
Copy link
Contributor

Previous behavior split the incoming token long-name value using the equal sign as the separator.
This would cause an option's value containing spaces to get truncated.
New behavior does regex. match to make sure format is correct and gets the full value.

@billbogaiv
Copy link
ContributorAuthor

billbogaiv commented Jul 20, 2016

To achieve same behavior contained within PR using existing functionality, I need to pass arguments like:

./app --option "first name=Bill;last name=Boga"

@billbogaivbillbogaiv changed the title Allow spaces when tokenizing option-value[WIP] Allow spaces when tokenizing option-valueJul 20, 2016
Previous behavior split the incoming token long-name value using the equal sign as the separator. This would cause an option's value containing spaces to get truncated. New behavior does regex. match to make sure format is correct and gets the full value.
@billbogaivbillbogaivforce-pushed the allow-spaces-when-tokenizing-option-value branch from 0681660 to 2912a6fCompareJuly 20, 2016 16:33
@billbogaivbillbogaiv changed the title [WIP] Allow spaces when tokenizing option-valueAllow spaces when tokenizing option-valueJul 20, 2016
@nemec
Copy link
Collaborator

Hi @billboga based on the code you replaced I think the problem was actually the = rather than spaces. In any case you've fixed the issue, so thanks for contributing!

@nemecnemec merged commit c98c643 into gsscoder:masterJul 20, 2016
@billbogaiv
Copy link
ContributorAuthor

Yeah, I had two different thoughts in my head when I was typing. What you wrote is what I meant 😄.

@billbogaivbillbogaiv deleted the allow-spaces-when-tokenizing-option-value branch July 20, 2016 20:08
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@billbogaiv@nemec