You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In v2.0.0 we introduced the ICommandLineArgumentsParser (#8) and IHelpWriter (#11) interfaces but for a TypeParser there's no interface. For consistency, we should add a 'ITypeParser` interface too, so users don't need get confused about sometimes having to extend an abstract class and sometimes implement an interface.
Proposal:
publicinterfaceITypeParser{/// <summary>/// Gets the <see cref="Type"/> this <see cref="TypeParser{T}"/> handles/// </summary>TypeType{get;}/// <summary>/// Tries to parse the specified value to the specified parse result/// </summary>/// <param name="value">/// The value to parse/// </param>/// <param name="parseResult">/// The parsed value/// </param>/// <returns>/// True if value was converted successfully; otherwise, false/// </returns>boolTryParse(stringvalue,outobjectparseResult);}
We must also update the configuration and all usages to support the interface instead of the current abstract base class TypeParser.
The text was updated successfully, but these errors were encountered:
In v2.0.0 we introduced the
ICommandLineArgumentsParser
(#8) andIHelpWriter
(#11) interfaces but for aTypeParser
there's no interface. For consistency, we should add a 'ITypeParser` interface too, so users don't need get confused about sometimes having to extend an abstract class and sometimes implement an interface.Proposal:
We must also update the configuration and all usages to support the interface instead of the current abstract base class
TypeParser
.The text was updated successfully, but these errors were encountered: