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.

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

Specify cmd arg names (metavars), et al. #3626

Merged
merged 5 commits into from
Apr 18, 2020
Merged

Specify cmd arg names (metavars), et al. #3626

merged 5 commits into from
Apr 18, 2020

Conversation

jorgeorpinel
Copy link
Contributor

@jorgeorpinel jorgeorpinel commented Apr 12, 2020

  • ❗ I have followed the Contributing to DVC checklist.

  • 📖 If this PR requires documentation updates, I have created a separate PR (or issue, at least) in dvc.org and linked it here. If the CLI API is changed, I have updated tab completion scripts.

  • ❌ I will check DeepSource, CodeClimate, and other sanity checks below. (We consider them recommendatory and don't expect everything to be addressed. Please fix things that actually improve code or fix bugs.)

Thank you for the contribution - we'll try to review it as soon as possible. 🙏

@codecov
Copy link

codecov bot commented Apr 12, 2020

Codecov Report

Merging #3626 into master will decrease coverage by 0.01%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #3626      +/-   ##
==========================================
- Coverage   90.89%   90.88%   -0.02%     
==========================================
  Files         153      153              
  Lines        9571     9571              
==========================================
- Hits         8700     8699       -1     
- Misses        871      872       +1     
Impacted Files Coverage Δ
dvc/command/add.py 100.00% <ø> (ø)
dvc/command/data_sync.py 100.00% <ø> (ø)
dvc/command/gc.py 91.30% <ø> (ø)
dvc/command/get.py 91.89% <ø> (ø)
dvc/command/imp.py 86.36% <ø> (ø)
dvc/command/imp_url.py 100.00% <ø> (ø)
dvc/command/ls/__init__.py 88.88% <ø> (ø)
dvc/command/repro.py 100.00% <ø> (ø)
dvc/command/run.py 89.36% <ø> (ø)
dvc/command/update.py 86.36% <ø> (ø)
... and 4 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 11e56db...91647ca. Read the comment docs.

@jorgeorpinel

This comment has been minimized.

@shcheklein

This comment has been minimized.

@jorgeorpinel

This comment has been minimized.

@@ -53,6 +53,7 @@ def add_parser(subparsers, parent_parser):
"-f",
"--file",
help="Specify name of the DVC-file this command will generate.",
metavar="<filename>",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure how this is better than -f FILE. <> look out of place here, and I don't really see the value, sorry.

Copy link
Contributor

@efiop efiop Apr 16, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But ok, if you want to, sure, lets do it this way. Please remove "Draft" flag from your PR.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think, the value can be better seen here - https://dvc.org/doc/command-reference/run#run

check with what dvc run outputs.

Copy link
Contributor Author

@jorgeorpinel jorgeorpinel Apr 16, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ruslan, 2 benefits (besides matching the docs which we already changed 😅):

  • The existing param names aren't descriptive. FILE isn't the best example of this but e.g. --outs OUTS why repeat the option name when the param name can hint to what kind of argument is accepted.
  • We didn't like how upper case looked in the docs. Looks like we're yelling haha. We checked Git and noticed they use <> e.g. https://git-scm.com/docs/git-commit

@jorgeorpinel jorgeorpinel changed the title Specify cmd arg names (metavars) Specify cmd arg names (metavars), et al. Apr 17, 2020
@jorgeorpinel jorgeorpinel marked this pull request as ready for review April 17, 2020 03:02
"Type of metrics (json/tsv/htsv/csv/hcsv). "
"Type of metrics (json/yaml). "
Copy link
Contributor Author

@jorgeorpinel jorgeorpinel Apr 17, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note I changed these too (in 5559ff6) per #3409 and #3572. Cc @dmpetrov

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

dvc: meaningful option arguments Consistent subcommand order
3 participants