Consider a different CLI framework? #205
Replies: 1 comment
-
I have to say that I’m currently rather hesitant to consider switching away from kong, also since it’s a “low-leveled” change that would require extensive testing. (Not just all the features, behaviour, and edge-cases, but also compatibility of different shells and operating systems.) The whole kongplete/completions topic is a bit unfortunate for sure, but it’s still a manageable shortcoming, and the rest of kong works pretty well overall. On the other hand, it would be interesting to see how the setup would look with Cobra. So if you (@chairmank, or anyone else) are motivated to explore this, feel free to go ahead and create a spike/POC. But there still is the risk that I have to put this topic on hold, or suspend it altogether. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
The klog CLI is currently implemented with kong. Back when I started the project, I didn’t have a strong reason to choose kong over something else, and apart from a few minor shortcomings it turned out to work well.
I’m not generally opposed to migrating from kong to something else (e.g. Cobra), but I have to admit that it wouldn’t be super important to me at this point. The shortcomings are currently manageable, and my overall experience with kong has been very positive.
Advantages of kong
struct’s and re-using them through regular composition is both straightforward to work withmainpackage.klog totalcommand, for example.)Shortcomings of kong
Beta Was this translation helpful? Give feedback.
All reactions