bonzai/README.md

37 lines
1.6 KiB
Markdown
Raw Normal View History

2022-02-17 22:15:16 +00:00
# Bonzai, Well-Tended CLI Command Trees for Gophers
2022-02-15 04:04:15 +00:00
2022-02-17 22:15:16 +00:00
## "It's spelled bonsai/banzai."
2022-02-15 04:04:15 +00:00
2022-02-15 04:56:21 +00:00
We know. The domains were taken. Plus, this makes it more unique and
easier to find once you know the strange spelling we chose to use. Sorry
if that triggers your OCD.
2022-02-17 22:15:16 +00:00
On a lighter note, it just so happens that "banzai" means 'a traditional
Japanese idiom meaning "ten thousand years" of long life,' a cheer used
in celebrations. So combining the notion of a happy, little,
well-manicured, beautiful tree and "ten thousand years of long life"
works out just fine for us.
2022-02-15 04:56:21 +00:00
Then, of course, there's the image of Buckaroo invoked every time we say
the name. In fact, I think we have our new theme song.
2022-02-17 21:52:01 +00:00
## Example GitHub Template
<https://github.com/rwxrob/template-bonzai>
## Design Considerations
* **Promote high-level package library API calls over Cmd bloat.** Code
belongs in package libraries, not Cmds. While Bonzai allows for rapid
applications development by putting everything initially in Cmd
Methods, Cmds are most designed for documentation and completion, not
heavy Method implementations. Eventually, most Method implementations
should be moved into their own package libraries, perhaps even in the
same Go module. Cmds should *never* be communicating with each other
directly. While the idea of adding a Channel attribute was intriguing,
it quickly became clear that doing so would promote too much code and
tight coupling --- even with channels --- between specific commands.
Cmds should be *very* light. In fact, most Cmds should assign their
Method directly from one matching the Method function signature in a
callable, high-level library.