-
Notifications
You must be signed in to change notification settings - Fork 3
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
enhancement!: CLI overhaul #299
Conversation
@korikuzma what would you think about shortening the options to
|
@jsstevenson to confirm, |
Co-authored-by: Kori Kuzma <[email protected]>
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.
🚀
close #293
close #217
progress on #298
stuff I did:
gene-normalizer
) and then different actions are commands (eggene-normalizer update
).sources
are now arguments, not an option. Since the number of sources can be 0 to n, I think it makes more sense to be used as an argument instead of a param passed to an option (avoids the quoting, spacing etc stuff).--silent
option to suppress feedback to console (false by default) in cases like pipelines that process stuff going to stdout. Addresses Database endpoint usage feedback #217 with a very stringent check (value must beTrue
, can't just be truthy, so no accidental silencing - hence thenoqa
).gene.etl.update
. That way they can easily be used programmatically (this is something that Thera-Py does with the Disease Normalizer, for example).The updated docs page looks like this: https://gene-normalizer--299.org.readthedocs.build/en/299/managing_data/loading_and_updating_data.html
And this is what the help looks like for the
update
command: