dvc: update cmd output strings to match docs#3471
Conversation
| metrics_add_parser.set_defaults(func=CmdMetricsAdd) | ||
|
|
||
| METRICS_MODIFY_HELP = "Modify metric file options." | ||
| METRICS_MODIFY_HELP = "Modify metric file values." |
There was a problem hiding this comment.
it should be options.
modifying values sounds like we actually modify metric values.
it is about setting up metric file settings (type, path, etc), not modifying metric values
There was a problem hiding this comment.
I see. I'll update this... ⏳ but still need the PR for other strings.
There was a problem hiding this comment.
What about "default formatting"? See latest version here and in treeverse/dvc.org/pull/1014
There was a problem hiding this comment.
default formatting options is still better? )
There was a problem hiding this comment.
I'm trying to avoid term "option" here since there are also command options (CLI flags) and config options (DVC settings) and it gets confusing some times in the explanations.
There was a problem hiding this comment.
Yep, I got the idea. I think it's almost impossible to avoid unfortunately in general (even if it works in this case). At least I was not able to find a good solution - may be even primarily I never thought that it's a really big deal - usually it's clear from the context. And can add more words when it's not clear from the context I think.
There was a problem hiding this comment.
I think I managed to avoid the term everywhere actually 🙂 assuming we let this one through. Yes it's not always a big deal but in this case and others I changed I thought it was confusing since all the "option" concepts are used in the same doc or even section of the doc sometimes.
using term "formatting" instead of "options"
It's a public fn after all. Similar to Repo class
|
|
||
| # Pull | ||
| PULL_HELP = "Pull data files from a DVC remote storage." | ||
| PULL_HELP = "Download tracked files or directories from remote storage." |
There was a problem hiding this comment.
Not sure pull and fetch help messages are different enough now. But it is definitely not worse.
There was a problem hiding this comment.
Good point. I'm just copying from https://dvc.org/doc/command-reference/fetch and https://dvc.org/doc/command-reference/pull here. This whole PR is about matching docs which I think is desirable but if not, please lmk!
| list_parser.add_argument( | ||
| "url", | ||
| help="Supported urls:\n" | ||
| "/path/to/file\n" |
There was a problem hiding this comment.
Not sure why are we getting rid of these useful examples. In favor of docs?
There was a problem hiding this comment.
Yeah for consistency with get and import and so the output here is shorter. We could go the opposite way and list all the examples in all these commands if that's preferable. Or we could add a link to the cmd ref in each one. Please lmk, happy to change it.
| metrics_modify_parser.set_defaults(func=CmdMetricsModify) | ||
|
|
||
| METRICS_REMOVE_HELP = "Remove files's metric tag." | ||
| METRICS_REMOVE_HELP = "Stop tracking a metric file." |
There was a problem hiding this comment.
This might be confusing. We are not stopping tracking the file but rather un-marking it as a metric.
There was a problem hiding this comment.
True. I'm updating this one and metrics add, as well as the cmd refs. See f262f48 and treeverse/dvc.org/pull/1072. Thanks!
| pipeline_show_parser.set_defaults(func=CmdPipelineShow) | ||
|
|
||
| PIPELINE_LIST_HELP = "List pipelines." | ||
| PIPELINE_LIST_HELP = "List connected groups of stages (pipelines)." |
There was a problem hiding this comment.
Why are we making this clarification here, but not in other places? pipeline is self descriptive enough, I don't think it needs a "connected groups of stages"
There was a problem hiding this comment.
Good question. Again, this is to match docs, https://dvc.org/doc/command-reference/pipeline/list specifically.
but not in other places
The only other place really is pipeline show which reads "Show stages in a pipeline." This one also mentions both terms "stage" and "pipeline" so it's similarly clear, I think.
| fix_subparsers(remote_subparsers) | ||
|
|
||
| REMOTE_ADD_HELP = "Add remote." | ||
| REMOTE_ADD_HELP = "Add a new data remote." |
There was a problem hiding this comment.
Are we sure we need data here? Won't it be confusing in regards to models and such?
There was a problem hiding this comment.
Sorry to repeat the same answer haha but just matching docs here (https://dvc.org/doc/command-reference/remote/add).
For consistency, we use the term "data remote" in remote subcommands cmd refs (not in other docs though). This is kind of arbitrary, I agree on that. Would you prefer a different standard? Happy to update everywhere.
|
|
||
| def add_parser(subparsers, parent_parser): | ||
| REMOVE_HELP = "Remove DVC-file outputs." | ||
| REMOVE_HELP = "Remove data files or directories tracked by DVC." |
There was a problem hiding this comment.
This is not only about data, but about stages/models/etc too.
There was a problem hiding this comment.
Hmmm OK changed to "Remove DVC-tracked files or directories." both here and in the cmd ref now. Better? The part about removing entire stage files is explained in the cmd ref desc.
| def add_parser(subparsers, parent_parser): | ||
| REPRO_HELP = "Check for changes and reproduce stages and dependencies." | ||
| REPRO_HELP = "Reproduce complete or partial pipelines" | ||
| " by executing their stages." |
There was a problem hiding this comment.
Since we have dvc run command, we use the term "execute" a lot in the repro cmd ref (https://dvc.org/doc/command-reference/repro).
|
Sorry for the delay. |
|
Ok, merging for now. Will try to keep an eye on the docs PRs. |
to match treeverse/dvc.org/pull/1014
and now treeverse/dvc.org/pull/1040 too
❗ Have you followed the guidelines in the Contributing to DVC list?
📖 Check this box if this PR does not require documentation updates, or if it does and you have created a separate PR in dvc.org with such updates (or at least opened an issue about it in that repo). Please link below to your PR (or issue) in the dvc.org repo.
❌ Have you checked DeepSource, CodeClimate, and other sanity checks below? We consider their findings recommendatory and don't expect everything to be addressed. Please review them carefully and fix those that actually improve code or fix bugs.
Thank you for the contribution - we'll try to review it as soon as possible. 🙏