Phew, it's been a busy day! So, today, I made a new NuGet package. Except, I can't actually upload it to NuGet for a month because I neglected to updated my e-mail address from the old company address. Microsoft does let you change your e-mail address from one that doesn't exist any more, but they make you wait 30 days to make absolutely sure that it isn't a case of attempted hijacking.
So, what does this NuGet package do? It parses command-lines. It's based on one I made years ago as a personal project and then later made use of in code I wrote for iQmetrix. In the work I did today, though, I reworked/rewrote it significantly based on my experience using it in its initial design.
The command-line parser project, which is fully configured for deployment to NuGet once the time comes around, and which is fully unit tested, is some 1,997 lines of code. Writing the tests to cover the implementation and hammer out bugs in it was enough effort that I decided to get myself sorted out with Visual Studio Code, as it has considerably better source introspection than VIM 😛
Then I updated the project I've been tracking here to use this command-line parser (I had a particular switch in mind when I started this), and reworked its entrypoint method. It was hosting an implementation class for testing purposes, but the next stage of testing, when I get there, is going to be of the service I'm implementing itself.
GitHub: DeltaQ.CommandLineParser
Stats:
-
Current line count: 4,046
- Plus 1,997 lines in a subsidiary project. (I won't report this every time.)
- Passing tests: 42, usually
- Unreliable tests: 1
- Tested classes: 11
- Untested classes: 3
- TODOs: 8
No comments:
Post a Comment