Closed astrohart closed 3 years ago
One of the reasons I started Fluent Command Line Parser is because I didn't like using any of the existing CLPs that required attributes decoration. I wanted to keep the CLP logic completely seperate and I felt that attributes didn't allow that.
Plus I liked using fluent api style, hence the name.
I'd like to just have the parser eat my custom command line info class and not have to call Setup for each and every argument. I'd be fine decorating the properties of my POCO with attributes that would allow the library to be used like:
The
[Option()]
(or whatever you want to call them) would do all the calls toSetup
for me, so that then I just fling myApplicationArguments
POCO at the ctor of theFluentCommandLineParser
class through its generic type parameter and then callParse
right away:Sooo much less code than:
And more extensible, too --- since I can then just add new properties to the POCO.