I am linting (or trying to) a non nf-core pipeline...
# tools
r
I am linting (or trying to) a non nf-core pipeline build with the template. It looks like the linting exists after the first issue:
Copy code
nf-core/tools version 4.1.0 - <https://nf-co.re>


INFO     Testing pipeline: 
INFO     Using found ORCID 
INFO     Saving metadata file to 
INFO     Generated container configs for the pipeline.
ERROR    [✗] Pipeline schema does not follow nf-core specs:
          Default parameters are invalid: '[]' is not of type 'array'
ERROR    [✗] Pipeline schema does not follow nf-core specs:
          Default parameters are invalid: '[]' is not of type 'array'
CRITICAL Critical error: [✗] Pipeline schema does not follow nf-core specs:
          Default parameters are invalid: '[]' is not of type 'array'
INFO     Stopping tests...
is there a way to make it run through? I don't really want to go through fixes first
m
Delete mahesh
shakefist 1
(sorry, just a joke)
add schema to the linting test you want to skip
or add whatever fails to the things you want to skip
you can get a pretty bare bone skeleton if you do that, and it actually passes linting
r
started going the other way and run the lint tests by key , although some don't seem to exist? I'll collect them first and then open an issue
Copy code
❯ nf-core pipelines lint --key included_configs


                                          ,--./,-.
          ___     __   __   __   ___     /,-._.--~\
    |\ | |__  __ /  ` /  \ |__) |__         }  {
    | \| |       \__, \__/ |  \ |___     \`-._,-`-,
                                          `._,._,'

    nf-core/tools version 4.1.0 - <https://nf-co.re>


CRITICAL Test name not recognised: 'included_configs'
m
ooh, that's a nice idea, I LOVE IT
I often get stuck on a single lint test, and I have to rerun ALL tests just to get to that one
r
version_consistency also fails
shakefist 1