As part of my “build things that help me build the next thing better and faster” plan, I needed to update my argument parsing NuGet package, ScottLilly.ArgumentParser, for one of those upcoming apps.
The package was originally written to parse a string in Twitch chat, for some chat games I wrote. The command line app I’m working on (CodeBundler) needed a bit more capabilities with parsing its possible incoming arguments – things like multi-character strings as indicators for the arguments and improvements around key/value arguments.
CodeBundler is an app to create a single text file (for the command line version) or textbox string (for the WPF version) of all code files in a Visual Studio solution, project, disk directory, or user-selected list of files. Then, you can paste that text into an LLM with a large context window and ask the LLM questions about the complete codebase.
Progress on CodeBundler is pretty good, and I may be able to release a version this weekend. The WPF and logic parts look good. I just need to integrate the new ArgumentParser package in the command line project and finish it.
Hopefully, that all goes smoothly. Although, I won’t be surprised if I need to make another change or two to ArgumentParser and release a new version.
I expect CodeBundler will help me build more of the programming productivity tools I have planned, which will ultimately lead to a commercial product I want to release (more on that later).
I also improved ArgumentParser’s README file and a few things in the build and deploy process, like tagging the version on the code and putting the release on GitHub.
There are still build, packaging, and release steps I plan to automate. I should probably get to those sooner, rather than later, so I can use them with the rest of the tools on my development timeline.
That’s everything for now. I am excited about the little process improvements I’ve already been able to make and am really excited about where this may ultimately end up.