Skip to content

Latest commit

 

History

History
219 lines (162 loc) · 9.8 KB

CHANGELOG.md

File metadata and controls

219 lines (162 loc) · 9.8 KB
Raw

Changelog

Unreleased

Enhancements:

  • @bjorg: support SingleOrNoValue notation. --option[:value]
  • Support the POSIX convention for cluster multiple options. For example, -ixd is treated the same as -i -x -d. Resolved #93.
  • New type: Pager. Provides a simple interaction model for displaying console output in a pager.
  • Display help text using the less pager on macOS/Linux.
  • Make suggestions when invalid options or commands are used, but there is a valid one that is similar. (Thanks to @MadbHatter for doing the inital work on this.)

Details:

  • Clustering options: I've added this behavior as the new default, but only if I think it won't interfere with existing apps. If it causes issues or you don't like clustering, you can disable this by setting CommandLineApplication.ParserSettings.ClusterOptions = false, or adding [Command(ClusterOptions = false)]. To preserve compatibilty with existing apps, this behavior is off if you have configured options with short names with multiple characters. In a future version, this will cause an error unless you set ClusterOptions = false.
  • Pager: this is the new default for showing help text. The pager should have graceful fallback to regular stdout when there are issues launching less, or when stdout is redirected into a pipe.

v2.2.5

July 1, 2018

Bug fixes:

  • @bording and @SeanFeldman: Unable to create new instance of CommandOption<T> for type that is already registered

Minor improvements:

  • Started code signing the NuGet package and binaries
  • @jerriep: added documentation for response file parsing

v2.2.4

May 24, 2018

Bug fixes:

  • @liamdawson: support parsing System.Uri
  • Fix #101 - Update DotNetExe.FullPath to honor the DOTNET_ROOT environment variable as a fallback

v2.2.3

May 10, 2018

Minor improvements:

  • Make it easier to override the version text shown when --version is specified.
  • Make DefaultHelpTextGenerator's constructor protected
  • Fix DebugHelper.HandleDebugSwitch

v2.2.2

April 28, 2018

Minor improvement:

  • Add conventions from attributes that implement IConvention and IMemberConvention
  • Add a help option by default as long as it doesn't conflict with existing options

v2.2.1

April 10, 2018

Bug fixes:

  • Don't assign option and argument options if no value was provided, preserving the default CLR value unless there is user-input.
  • Fix ShowHint() to use ShortName or SymbolName if OptionHelp.LongName is not set
  • Fix #85 - lower priority of resolving AdditionalServices after most built-in services
  • Fix #79 - OnValidate callbacks invoked before property valueswere assigned

Minor improvements:

  • Improve help text generation. Align columns, show top-level command description, and add protected virtual API to DefaultHelpTextGenerator to make it easier to customize help text

v2.2.0

March 30, 2018

  • Added support for command validators using CommandLineApplication.Validators and added a new OnValidate convention
  • Fix minor bug in ArgumentEscaper where some strings were not properly escaped
  • Update to System.ComponentModel.Annotations 4.4.1 (netstandard2.0 only)
  • @atruskie: Ensure ValueParsers are inherited in subcommands

v2.2.0-rc

March 23, 2018

New API:

  • @atruskie: Added support for user-defined value parsers using IValueParser and CommandLineApplication.ValueParsers.
  • Added support for Option<T> and Argument<T>
  • Added IValidationBuilder<T>
  • Added .Accepts().Range(min, max) for int and double type arguments and options

Enhancements:

  • Parse these values to boolean: T, t, F, f, 0, 1

Removed:

  • Removed support for mapping Tuple<bool,T> to CommandOptionType.SingleOrNoValue. ValueTuple<bool,T> is still present.

v2.2.0-beta

March 7, 2018

New features:

  • Add CommandOptionType.SingleOrNoValue. Options of this type can be a switch, or have a value but only in the form --param:value or --param=value.
  • Support mapping Tuple<bool,T> and ValueTuple<bool,T> to CommandOptionType.SingleOrNoValue
  • Added CommandLineApplication<TModel>. This allows associating an application with a specific .NET type
  • Convention API. Adds support for writing your own conventions to convert command line arguments into a .NET type
  • @sebastienros - Support for case-insensitive options
  • Add support for constructor injection and dependency injection by providing a custom service provider

v2.2.0-alpha

Feb. 15, 2018

New features:

  • Added more validation attributes.
    • Add the [FileExists] attribute
    • Add the [FileOrDirectoryExists] attribute
    • Add the [DirectoryExists] attribute
    • Add the [LegalFilePath] attribute
    • Add the [AllowedValues] attribute
  • Added a new, fluent API for validation.
    • Added Option().Accepts() and Argument().Accepts()
    • Add .ExistingFile()
    • Add .ExistingFileOrDirectory()
    • Add .ExistingDirectory()
    • Add .EmailAddress()
    • Add .LegalFilePath()
    • Add .MinLength(length)
    • Add .MaxLength(length)
    • Add .RegularExpression(pattern)
    • Add .Values(string[] allowedValues)

API improvements:

  • Support parsing enums
  • @atruskie - Support for parsing double and floats
  • @rmcc13 - HelpOption can be set to be inherited by all subcommands
  • Add VersionOptionFromMember to use a property or method as the source of version information

v2.1.1

Dec. 27, 2017

Bug fixes:

  • Do not show validation error messages when --help or --version are specified
  • Fix help text to show correct short option when OptionAttribute.ShortName is overriden

v2.1.0

Dec. 12, 2017

New features:

  • Attributes. Simplify command line argument definitions by adding attributes to a class that represents options and arguments.
    • Options defined as [Option] or [Argument], [Subcommand].
    • Command parsing options can be defined with [Command] and [Subcmomand].
    • Special options include [HelpOption] and [VersionOption].
    • Validation. You can use [Required] and any other ValidationAttribute to validate input on options and arguments.
  • Async from end to end. Using C# 7.1 and attribute binding, your console app can be async from top to bottom.
  • Required options and arguments. Added CommandOption.IsRequired() and CommandArgument.IsRequired().

New API

  • @demosdemon - added Prompt.GetSecureString
  • Prompt.GetYesNo, Prompt.GetPassword, and more. Added API for interactively getting responses on the console.
  • Added OptionAttribute, ArgumentAttribute, CommandAttribute, SubcommandAttribute, HelpOptionAttribute, and VersionOptionAttribute.
  • CommandLineApplication.Execute<TApp>() - executes an app where TApp uses attributes to define its options
  • CommandLineApplication.ExecuteAsync<TApp>() - sample thing, but async.
  • CommandLineApplication.ResponseFileHandling - the parser can treat arguments that begin with '@' as response files. Response files contain arguments that will be treated as if they were passed on command line.
  • @couven92 - added overloads for few new CommandLineApplication.VersionOptionFromAssemblyAttributes and .VerboseOption extension methods

Minor bug fixes:

  • Add return types to .VerboseOption() and ensure .HasValue() is true when HelpOption or VerboseOption are matched
  • Fix a NullReferenceException in some edge cases when parsing args
  • Fix bug where DotNetExe.FullPath might return the wrong location of the dotnet.exe file

Other:

  • @kant2002 - added a new sample to demonstrate async usage

v2.0.1

Oct. 31, 2017

  • @couven92 - Add support for .NET Standard 1.6

v2.0.0

Sep. 16, 2017

  • Initial version of this library.
  • Forked Microsoft.Extensions.CommandLineUtils
  • Renamed root namespace to McMaster.Extensions.CommandLineUtils
  • Added a handful of new API
  • Updated TFM to support .NET Standard 2.0