Replies: 1 comment
-
For showing usage inside of
Wait, that isn't quite usage. Its sometimes usage and sometimes an example. It also is sometimes aligned and sometimes not. Alignment helps with distinguishing it but also takes up even more space. I think I would lean towards only showing usage. The big question is how are people using the I also feel like for a lot of tooling commands, the arguments are optional or obvious, removing a lot of the benefit. The one thing I could see being a point towards usages is the out of box experience for people unfamiliar with this area of tooling (students?). This isn't a "no". I am open to other's thoughts on this.
it might be good to show examples of APIs for what you are wanting. Looking at that |
Beta Was this translation helpful? Give feedback.
-
I have seen some CLI tools special handle having examples for subcommands.
For example:
cmd help:
cmd run help:
the second one is quite simple to add, and the first one as well with a custom help template, but would be nice if we didnt have to have a custom help template and a lot of after_help to handle examples. so basically having examples built-in would be nice
Beta Was this translation helpful? Give feedback.
All reactions