``` Error modules.config:912:101: `meta` is not d...
# help
j
Copy code
Error modules.config:912:101: `meta` is not defined
  │ 912 | db_name}" } : { "${meta.id}_${meta.run_accession}_${meta.db_name}" }
  ╰     |
confused dog 1
excuseme 1
f
I haven't seen an issue with this. What does the whole block look like?
j
Essentially we use
meta
everywhere in
prefix
Oh wait...
I've had an idea
OK yeah this seems to satisfy linting:
Copy code
ext.prefix = params.perform_runmerging ? { "${meta.id}_${meta.db_name}.sylph" } : { "${meta.id}_${meta.run_accession}_${meta.db_name}.sylph" }
to
Copy code
ext.prefix = { params.perform_runmerging ? "${meta.id}_${meta.db_name}.sylph" :  "${meta.id}_${meta.run_accession}_${meta.db_name}.sylph" }
Dunno why that makes a difference...
m
{} delays
n
Probably a false positive in the parser, but it would kind of make sense to only supply one closure for clarity
j
Yeah I recognised it was suboptimal, but I didn't see why it wouldn't make sense
Anyway VScode isn't complaining now anyway