toggler VS cobra

For example in this project : https://github.com/toggler-io/toggler I use a modular and DRY TDD approach where I have a way to composite testing components. The tests are not aware of how a component needs to be initialized for the test, so for the majority of time I initialize interactors with in memory fakes as dependencies, which makes the whole testing suite super nimble. This gives me fast feedback loops, but during CI/CD pipeline I can swap out the fakes with real components like postgres for storage, and then suddenly all the unit tests of the business logic interactors become a full fledged end to end test to confirm an as real life as possible usage.

We can use the flag with --date or -date, Go already does the automatic check. We can make our entire boilerplate with this approach, but let's make it a little easier and use the Cobra CLI package.

In this tutorial, we'll walk through the process of creating a simple command-line tool similar to curl using Go and Cobra, a CLI library for Go.

I use https://github.com/spf13/cobra religiously for this kind of thing - it handles all the annoying corner cases of parsing flags, and also has an intuitive notion of subcommands (with basic usage/help text generated) for picking which task you want to run with positional arguments.

We recently chose cobra[1] to create a cli application. It comes with so many best practices already packaged like autocompletions, help texts etc. etc.

[1]: https://github.com/spf13/cobra

github.com/spf13/cobra

I looked at the docs: https://cobra.dev/ ... and there are only examples on how to add new flags.

For installing Cobra-CLI you can go to Cobraor run go install github.com/spf13/cobra-cli@latest in the terminal.

In my build phase, I compile the source to create a k3sup binary and I also run the binary to generate shell script completions. Give kudos to this functionality which comes from spf13/cobra Go library for CLIs.

NWA is a command-line tool built on cobra. Here's an overview of NWA's commands: