-
Notifications
You must be signed in to change notification settings - Fork 85
Roadmap
siywilliams edited this page Apr 22, 2013
·
38 revisions
Some functional changes have been made which may impact existing behaviour.
A InvalidOptionNameException
is now thrown when setting up an Option if:
- A specified long Option name is a single char in length.
- A specified long Option name contains
:
or=
characters anywhere within it.
Changes have been kept to a minimal with the following changes made:
-
Setup<T>(string, string)
has been made obsolete, being replaced instead withSetup<T>(char, string)
. This is to better reflect through the Api that short Options should be a single character only. -
Setup<T>(string)
is no longer used to setup an Option with only a short name. Instead it is used to setup an Option with only a long name. This will initially result in anInvalidOptionNameException
raised when the method is invoked as long names must now be longer than a single character in length. If you require to setup an option with a short name only you should use theSetup<T>(char)
overload instead.