Chris Wright
Chris Wright
@bentsherman Is there any update on this issue? An option to disable the unhelpful automatic casting would be useful.
Then change it so its not 😉
In all seriousness, when using nf-core style parameter schemas there no source of truth for parameters. We have a lot of CI to ensure schemas and `params` are in sync....
@bentsherman is there any update on this. This is becoming a blocker for us.
Yes, a simple option to disable all casting of parameter values and leave developers to do it for themselves would work. > @bentsherman Is there any update on this issue?...
Thanks! I think as an interim solution we can then write a class to mutate `params` based on the content of an nf-core-style jsonschema document with type information.
You're dangerously close to making GroovyMake with Groovy code embedded in YAML 🤣 . Your choice is a conundrum, on the one hand it represents a loss of functionality to...
I can't tell who's violently agreeing with who. I think I'm violently agreeing with @ewels: use something generic like the nf-core schema for loading and understanding static data that may...
...and ~remove~ override nextflow's dodgy type casting in favour of whats declared in the schema
This is naturally not a single source of truth: its just a way of generating a secondary file which could become out of sync with the primary document, just like...