If the user leaves the db_extra line completely blank, it breaks the install because it inserts the word "None" into the dammit databases --install command
I managed to learn this because instead of running ./run_eelpond config.yaml annotate --print_params myself and copying out the text, I copied it directly from the helpful text box with the nice copy option in the documentation: https://dib-lab.github.io/eelpond/annotate/#configuring-the-annotate-subworkflow
If I run the command myself I do get db_extra: '' but in the docs, it has db_extra:. Editing the docs might save you from future lazy people like me complaining :)
Two things:
If the user leaves the db_extra line completely blank, it breaks the install because it inserts the word "None" into the
dammit databases --installcommandI managed to learn this because instead of running
./run_eelpond config.yaml annotate --print_paramsmyself and copying out the text, I copied it directly from the helpful text box with the nice copy option in the documentation: https://dib-lab.github.io/eelpond/annotate/#configuring-the-annotate-subworkflow If I run the command myself I do getdb_extra: ''but in the docs, it hasdb_extra:. Editing the docs might save you from future lazy people like me complaining :)