As we know now (I think so), nf-core conventions encompass the ones imposed by the language server, but do apply more restrictions. Under that, VSCode highlighting wil follow current Nextflow standards. But there isn't any ways to further restrict the language with, let's say, nf-core guidelines.
Please, add a configuration option (probably associated to a configuration file on the nf-core end) so we can apply extended community linting onto users modules and subworkflows that get submitted to libraries like nf-core or nf-neuro.
I know the nf-core/tools cli software is built to do such a review, but it's still not raising the errors on old DSL1 syntax (which may very well be non-nf-core-abiding synatx).
As we know now (I think so),
nf-coreconventions encompass the ones imposed by the language server, but do apply more restrictions. Under that, VSCode highlighting wil follow current Nextflow standards. But there isn't any ways to further restrict the language with, let's say,nf-coreguidelines.Please, add a configuration option (probably associated to a configuration file on the
nf-coreend) so we can apply extended community linting onto users modules and subworkflows that get submitted to libraries like nf-core or nf-neuro.I know the nf-core/tools cli software is built to do such a review, but it's still not raising the errors on old DSL1 syntax (which may very well be non-nf-core-abiding synatx).