You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latest template removed the libs directory, and moved any pipeline-specific functions into subworkflows/local/utils_nfcore_eager_pipeline/main (example from eager).
Now, we include these in the include block in each subworkflow:
include { addNewMetaFromAttributes } from '../../subworkflows/local/utils_nfcore_eager_pipeline/main'
When linting with nf-core lint we get the following warning: Included component 'addNewMetaFromAttributes' versions are not added in main.nf
It would be great to include a way to ignore specific includes when checking for versions during linting.
Given that some functions are imported in every local subworkflow, we end up with this warning showing up multiple times. I’m worried important warnings will end up lost in the sea of these warnings otherwise.
The text was updated successfully, but these errors were encountered:
Description of feature
The latest template removed the libs directory, and moved any pipeline-specific functions into
subworkflows/local/utils_nfcore_eager_pipeline/main
(example from eager).Now, we include these in the include block in each subworkflow:
When linting with nf-core lint we get the following warning:
Included component 'addNewMetaFromAttributes' versions are not added in main.nf
It would be great to include a way to ignore specific includes when checking for versions during linting.
Given that some functions are imported in every local subworkflow, we end up with this warning showing up multiple times. I’m worried important warnings will end up lost in the sea of these warnings otherwise.
The text was updated successfully, but these errors were encountered: