-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFC] improve generated boilerplate #12
Comments
spf13/cobra#1290 was also an issue pointing out that data races were detected in that default app. This will be something we need to check when we re-write the sample. |
#14 is a step forward.
|
This issue is being marked as stale due to a long period of inactivity |
This issue is being marked as stale due to a long period of inactivity |
I've found this issue and RFC because I was going to open an issue/question about the I've found a really nice article on how to structure a Cobra application, and this is what I am using as a guidance at the moment: https://carolynvanslyck.com/blog/2020/08/sting-of-the-viper/
Is this RFC going to be implemented? Or what's the state of it? 🙂 |
This issue is being marked as stale due to a long period of inactivity |
This issue is being marked as stale due to a long period of inactivity |
This issue is being marked as stale due to a long period of inactivity |
spf13/cobra#1614 (comment)
Multiple issues in the spf13/cobra repo were regarding the patterns of globals/init methods which made testing and growth difficult.
This linked issue properly points to the method (I think) most people eventually figure out for themselves.
Moved to this repo due to the CLI being split off.
The text was updated successfully, but these errors were encountered: