Unexpected error when a parameter isn't in the schema

[nvnieuwk]

When a parameter has been set in the nextflow.config file, but not yet in the schema, the pipeline will fail with this weird error (project is the name of the parameter added to the config):

N E X T F L O W  ~  version 23.04.0
Launching `main.nf` [sick_boltzmann] DSL2 - revision: bfa6b06e83
ERROR ~ JSONObject["project"] not found.

I think it would be best if a warning is returned instead stating that the parameter isn't in the schema instead of failing the pipeline entirely. (@mirpedrol?)

[mirpedrol]

Agree. I assume pipeline users will be the ones finding this error, and it's not in their hands to fix it.

[mirpedrol]

@nvnieuwk have you started working on that? Otherwise, I will try a fix :)

[nvnieuwk]

I've not done any work on this :)

[mirpedrol]

I think this was fixed with a previous PR, I can't reproduce the error with the current version, probably #51 ?
Can you confirm that the error is solved for you too?

[nvnieuwk]

I've tried it with the latest master branch and it still fails. I'll try and make a small reproducible example

[nvnieuwk]

Hmmm weird, I'm unable to get it to work in a small example... I'll investigate some more later today