fix: dataset naming #898
Merged
fix: dataset naming #898
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Panaetius
suggested changes
Jan 14, 2020
Member
Panaetius
left a comment
Panaetius
left a comment
There was a problem hiding this comment.
Thank you, looks good to me. Just a minor cleanup that could be added.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When creating a dataset, users now provide a
short_namewhich is easy to work with in a command line shell and an optionaltitlewhich is human-readable name for the dataset. Since all cli commands now work withshort_name, this PR also usesshort_nameconsistently in the command line.Fixes #876