jpdillingham/Utility.CommandLine.Arguments

Issues

• Trying to use negative double value cause Exception

  #70 opened 3 years ago by tundy
  1

• Argument starting with tilde (~) are not captured and left blank

  #69 opened 3 years ago by Barryrowe
  1

• Breaking changes for v6.0.0

  #68 opened 3 years ago by jpdillingham
  0

• Parse() dos not capture multiple values for repeated arguments

  #66 opened 3 years ago by jpdillingham
  1

• Documentation oversight

  #65 opened 4 years ago by GerryOnGithub
  1

• Fails to read argument strings starting with /

  #61 opened 4 years ago by StefanH-AT
  5

• Arguments using only long name?

  #62 opened 4 years ago by StefanH-AT
  1

• Breaking changes for v5.0.0

  #64 opened 4 years ago by jpdillingham
  0

• Arguments starting with non-Alpha characters followed by Forward slashes are dropped completely

  #60 opened 5 years ago by Barryrowe
  2

• Breaking changes for v4.0.0

  #59 opened 5 years ago by jpdillingham
  0

• Allow properties to be populated from environment variables

  #52 opened 5 years ago by jpdillingham
  1

• Subcommad support

  #53 opened 5 years ago by RajaSrinivasan
  2

• Remove support for unquoted forward slashes as values

  #57 opened 5 years ago by jpdillingham
  1

• Fix Travis CI configuration of sonarscanner

  #56 opened 5 years ago by jpdillingham
  0

• Argument values starting with non-word-characters are treated as operands

  #54 opened 5 years ago by montgomerybc
  0

• Breaking changes for v3.0.0

  #47 opened 6 years ago by jpdillingham
  0

• Implicit Type identification via stack inspection doesn't work when called from async methods

  #45 opened 6 years ago by jpdillingham
  0

• GetArgumentHelp() doesn't work with async methods

  #43 opened 6 years ago by jpdillingham
  0

• Properties backing arguments with multiple values not populated properly if short and long argument names are specified

  #15 opened 6 years ago by jpdillingham
  0

• Support enums

  #24 opened 6 years ago by jpdillingham
  0

• With .NET Core the executable is identified as an operand

  #30 opened 6 years ago by jpdillingham
  1

• Populate() does not work with .NET Core 2.x

  #40 opened 6 years ago by jpdillingham
  2

• Add support for default values

  #37 opened 6 years ago by jpdillingham
  1

• Investigate behavior of "clearing" existing values during Populate()

  #38 opened 6 years ago by jpdillingham
  1

• Target .NET Standard 2.0

  #29 opened 6 years ago by jpdillingham
  0

• Create a way to build a help

  #22 opened 6 years ago by JulioGold
  2

• Rename Extensions

  #25 opened 6 years ago by jpdillingham
  0

• Improper value propagation when a boolean flag is followed by an operand

  #28 opened 6 years ago by jpdillingham
  0

• Values can't start with a slash

  #26 opened 6 years ago by MatthiasJentsch
  2

• .net core support

  #20 opened 7 years ago
  1

• Null reference error

  #3 opened 8 years ago by MarkRK
  3