Declare the annotator click function as a console entry point, enabling vrs-annotate input.vcf --vcf_out=out.vcf rather than python3 src/ga4gh/vrs/extras/vcf_annotation.py input.vcf --vcf_out=out.vcf.
Open to suggestions on the command name. I'd prefer a structure more along the lines of vrs-annotate vcf input.vcf --vcf_out=out.vcf (i.e., vrs-annotate is the command, vcf is a subcommand) if we think there's a chance that other filetypes could be annotated in the future (in that case, we may want to alter the module name as well). Alternatively, though, the subcommand might be superfluous if the file argument has a suffix indicating the filetype.
Declare the annotator
click
function as a console entry point, enablingvrs-annotate input.vcf --vcf_out=out.vcf
rather thanpython3 src/ga4gh/vrs/extras/vcf_annotation.py input.vcf --vcf_out=out.vcf
.Open to suggestions on the command name. I'd prefer a structure more along the lines of
vrs-annotate vcf input.vcf --vcf_out=out.vcf
(i.e.,vrs-annotate
is the command,vcf
is a subcommand) if we think there's a chance that other filetypes could be annotated in the future (in that case, we may want to alter the module name as well). Alternatively, though, the subcommand might be superfluous if the file argument has a suffix indicating the filetype.