Open PonchoPowers opened 4 weeks ago
Not a biggie, but is the naming of classes going to be addressed.
CliConfiguration is ok I guess but then you have CliArgument and ArgumentArity.
It might be worth just ditching the Cli from the classes that have Cli in the naming?
CliOption and OptionValidation are another example, it almost makes the classes sound unrelated.
The naming doesn't really confirm as to how the rest of the .NET Framework is written too.
Related, but specific to files,
CliConfigurationException is in a file named CommandLineConfigurationException.cs
Not a biggie, but is the naming of classes going to be addressed.
CliConfiguration is ok I guess but then you have CliArgument and ArgumentArity.
It might be worth just ditching the Cli from the classes that have Cli in the naming?
CliOption and OptionValidation are another example, it almost makes the classes sound unrelated.
The naming doesn't really confirm as to how the rest of the .NET Framework is written too.