Skip to content
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.

Sign up for GitHub

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

Jump to bottom

clarify handling of command line options #254

Closed
ffromani opened this issue Nov 29, 2023 · 1 comment
Closed

clarify handling of command line options #254

ffromani opened this issue Nov 29, 2023 · 1 comment
Milestone
v0.19.0

Comments

@ffromani
Copy link
Collaborator

clarify expectations and handling of command line options. Should we expect two dashes for --options everywhere, including single-letter options? should it be --v or -v? or should we follow the -single-dash-everywhere go convention?
We need docs to set expectations and to follow them consistently in the codebase.
@ffromani ffromani mentioned this issue Nov 29, 2023
Closed
@ffromani
Copy link
Collaborator Author

handled by #257 and #255

@ffromani ffromani added this to the v0.19.0 milestone Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v0.19.0
Development

No branches or pull requests
1 participant
@ffromani