-
Notifications
You must be signed in to change notification settings - Fork 7
Support for helpUrl and improved help text and usage.md #72
base: master
Are you sure you want to change the base?
Conversation
Q: should I remove the exit codes from the README.md document since they are also documented in the usage.md file? Q: Should the localhost caveat be moved to the usage.md file? |
[-2 | --arg2 | --head] [-3 | --arg3 | --body] | ||
[--shardKey] [--no-strict] [--timeout] | ||
[--http] [--raw] [--health] | ||
`tcurl` <service> <endpoint> <options> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
`tcurl [OPTIONS] service endpoint`
The options are usually not enumerated in the synopsis of a man page, and typically are for usage on the command line.
A: yes, let’s DRY up the exit codes, making the usage.md the authority. Let’s add a link to README.md to usage.md to make it discoverable for casual visitors to the repository. A: yes, let’s move the caveat to the man page. |
Is this in a good place to rebase and land? @kriskowal @ShanniLi |
-3 --body <value> Set body to <value> | ||
--http <method> Use HTTP <method> instead of TCP | ||
--health Print health for <service> | ||
--raw Send header and body as binary diaray |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/diaray/data/
Consider breaking into a PR for the help URL feature and a separate PR for the help audit. |
The previous help text was more useful and the current help text did not make it obvious that you would get more detailed help information if you executed
tcurl --help
. I reverted to a style like the previous help text but better formatted. I also added support for a helpUrl option to be printed in the short help.