Skip to content

Conversation

do0om
Copy link
Contributor

@do0om do0om commented Jun 30, 2013

more information in the mail I sent you.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you update this because you use single quotes to wrap string values that can contain whitespace, such as 'my value'?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, but as I said, this implies change somewhere else that I didn't do.
I think I need to remove single quotes after because 'my value' needs to be in a string without the '

do0om added 4 commits July 1, 2013 17:05
Conflicts:
	FluentCommandLineParser/Internals/CommandLineOption.cs
	FluentCommandLineParser/Internals/Parsing/CommandLineParserEngineMark2.cs
	FluentCommandLineParser/InvalidOptionNameException.cs
	FluentCommandLineParser/OptionAlreadyExistsException.cs
	FluentCommandLineParser/Properties/AssemblyInfo.cs
This reverts commit 0af92ee.
@bastienJS
Copy link

Is this project still supported, I see the failed test which are very old... I am interested in implementing the .Validate(Predicate condition) method!

siywilliams added a commit that referenced this pull request Nov 6, 2014
Follows #23

- Test against parsing standard/uppercase/lowercase string values.
- Test to ensure that a custom enum parser is given priority over default one.
- Test that int32 are parsed into enum correctly.
Sign up for free to 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.

3 participants