-
Notifications
You must be signed in to change notification settings - Fork 15
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
ping --handshake-only
#524
Conversation
603309a
to
d6abb95
Compare
d6abb95
to
c52dc8a
Compare
c769953
to
afde59d
Compare
afde59d
to
624ba8d
Compare
[-j|--json] | ||
[-q|--quiet] | ||
[-Q|--query-versions] | ||
| --handshake-only (-u|--unixsock SOCKET) |
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.
This incorrectly omits all the other options in this case.
This is because visibility in optparse-appicative
can only be Internal
, Hidden
or Visible
.
There is no fourth visibility to hide an option in the full description and show it in the brief description.
So we either omit these options in the brief description here, or they will be doubled in the full description.
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.
Hum I see, there is no good solution in the current state.
@Jimbo4350> would be it acceptable to instead:
- Keep only one parser (e.g.
pPing
) and - Indicate in
-u/--unixsock
that this option requires--handshake-only
- Perform the check that if
-u
is specified, then so is--handhshake-only
, when the command starts to run? (as opposed to doing the check in the parser)
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.
Formatting is off. Can you run this through stylish?
https://github.com/input-output-hk/cardano-node-wiki/wiki/Style-guide#code-linting-and-formatting-tools
This PR is stale because it has been open 45 days with no activity. |
Since this is not a priority, I'm letting the stale bot do its thing. This PR (and the previous one) will still be there if we want to revisit. |
This PR is stale because it has been open 45 days with no activity. |
This issue was closed because it has been stalled for 60 days with no activity. |
Changelog
Context
issue
previous PR
How to trust this PR
Highlight important bits of the PR that will make the review faster. If there are commands the reviewer can run to observe the new behavior, describe them.
Checklist