Skip to content

Conversation

@m-malkowski
Copy link

No description provided.

nemec and others added 30 commits June 8, 2016 16:09
…t. Made easier to override by bring it up to the ParserSettings class.

Added ParserSettings.MaximumDisplayWidth property that will be passed to
HelpText

Added maxDisplayWidth params to several methods with a default of
DefaultMaximumLength if not provided

Added an attempt to set the MaximumDisplayWidth  in ParserSettings and
HelpText to Console.WindowWidth and if it isn't possible use
MaximumDisplayWidth instead.
Defaults to current consoles width if available otherwise uses default. Made easier to override by bring it up to the ParserSettings class.
The attribute Hidden has been added to OptionAttribute, ValueAttribute,
and VerbAttribute.  By default it is false.

Changes to support this new attribute so that if hidden it is not
visible in the help text, but is still usable if called correctly. If
you ask for help on a hidden verb you will get the help displayed but
hidden options will still be hidden. Allowing for hidden verbs with not
hidden options.

Resolves issue #263
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.
…tion-value

Allow spaces when tokenizing option-value
Implemented Hidden Verbs, Options and Values
Fixed typo.
Newer tools require some config changes. xUnit also has incompatibilities
with .Net 4.0 assemblies.
Also changed IList<Attribute> to IEnumerable<Attribute>.
…erence

Fix for missing author null reference (#332)
fix outdated README section under csharp with working example.
This reverts commit 4e15d55.
Add unit tests for TypeConverter for scalars (only). Add DotSettings.user
to .gitignore.
@nemec
Copy link
Collaborator

nemec commented Nov 5, 2016

I'm pretty sure I merged everything in the dotnet-core branch back into master, but if anything this merge should be going the other way: dotnet-core -> master

This branch will be deleted soon now that master has support for .net core, so I won't merge this. Have you noticed anything I should merge back into master?

@nemec nemec closed this Nov 5, 2016
@m-malkowski
Copy link
Author

@nemec Sorry, I didn't know the support is already there on master, as the readme says otherwise. Can we close / merge down this one and update the readme then?

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.

10 participants