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.
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
Big Bakta update #235
Big Bakta update #235
Changes from 8 commits
470ec8a
e0ff6f2
b9dd77e
1c96469
f567267
9b4148f
479708f
9f05ac4
41ce8f3
3bebde1
86c11b0
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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.
I am a bit confused about the new parameter:
--annotation_bakta_db
expects a path to a local DB (might be full or light, depends on what the user downloaded himself)while
--annotation_bakta_db_light
determines in the modules.config, if inBAKTA_BAKTADBDOWNLOAD
the ext.args--type
will be set tofull
orlight
:params.annotation_bakta_db_light ? '--type light' : '--type full'
Shouldn't this then be a boolean parameter with default
false
instead ofnull
? If no path to an existing baktaDB ist given via--annotation_bakta_db
, then the full bakta_db is downloaded unlessannotation_bakta_db_light
was set totrue
.Do we want the
light
or thefull
version to be default when downloading?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.
Ahh yes, that's why reviews are important :D The new parameter should of course be boolean.
I remember my reason for having
null
was that there was an issue withnf-core schema build
when puttingfalse
as default, but forgot to check/fix that.Default: I would go for
full
DB, but can test if there are big differences to thelight
DB in the output. If not, let's uselight
of course.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.
Maybe consider renaming
--annotation_bakta_db
to make clear that this is for a local installation. Something like--annotation_bakta_db_path
or--annotation_bakta_db_local
?I agree with the
full
db as default. Then the parameter--annotation_bakta_db_light
can just stay as it is.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.
I agree, we should disambiguate, and default should be set to a boolean not
null
. Another suggestion:Or something?