I've found a new linting error I've not had before with the latest version of tools. in #C062H82UCRG we have (admittedly ugly), parameter which takes a parameter string of it's own to pass to a tool:

--sourmash_build_dna_options '--param-string 'scaled=1000,k=31,noabund'

In the latest version of tools, I now get a linting error that the default in

nextflow.config

(above) doesn't match the default in the pipeline schema, which is

"default": "--param-string \\'scaled=1000,k=31,noabund\\",

╭─ [✗] 2 Pipeline Tests Failed ────────────────────────────────────────────────╮
│                                                                              │
│ nextflow_config: Config default value incorrect:                             │
│ params.sourmash_build_dna_options is set as --param-string                   │
│ \'scaled=1000,k=31,noabund\ in nextflow_schema.json but is --param-string    │
│ 'scaled=1000,k=31,noabund' in nextflow.config.                               │
│ nextflow_config: Config default value incorrect:                             │
│ params.sourmash_build_protein_options is set as --param-string               │
│ \'scaled=200,k=10,noabund\ in nextflow_schema.json but is --param-string     │
│ 'scaled=200,k=10,noabund' in nextflow.config.                                │
│                                                                              │
╰──────────────────────────────────────────────────────────────────────────────╯

But if I remove the escapes, then I hit the problem where the schema builder ALSO complains:

:sparkles: Default for 'params.sourmash_build_dna_options' in the pipeline config does not match schema. (schema: '<class 'str'>: --param-string
'scaled=1000,k=31,noabund''  | config: '<class 'str'>: --param-string 'scaled=1000,k=31,noabund'). Update pipeline schema? [y/n]: y

and then when I let it fix it, I lose the final

'

...