-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nested params #15
Comments
I just realized that it does work to define params using standard groovy for nested objects, as in: when {
params {
output_dir = "tests/results"
outer = [inner: 'value']
}
... It's not a bad workaround, but it would be nice to have a unified syntax between Nextflow and |
Thanks for reporting this issues and giving nf-test a try. It definitely makes sense to use the same syntax as Nextflow. 👍 We will try to fix it. Passing params as a file is not yet supported, but we will think about it... |
We tried doing that and it is working for us: |
Thank you @Khushbu04in! I will reuse your code to create a
Best, lukas. |
Passing params from a file (json, yaml, etc) is almost a must have feature, IMO. We have big datasets we'd like to test and it would (will) be very painful to convert the json to the groovy object notation. I'm not sure of anyway to do it other than by hand. @Khushbu04in could you share your full approach? I'm not sure how to get the data into the I can do this outside of
... and it works in the sense that But if I then do this:
I get this:
|
This feature is now available in version 0.7.1 👉 https://code.askimed.com/nf-test/testcases/global_variables/ |
Thank you for creating this package! I love the simplicity and flexibility. Unfortunately, I have run into an issue that will make it difficult to use
nf-test
in practice. Most Nextflow pipelines have some degree of nesting in their params, e.g.:When running a test that includes nested params, I get an error. As an example:
Running this, I get:
Am I specifying the params incorrectly or are they not yet fully supported within
nf-test
? Also, is it possible to pass params as a file (i.e. JSON or YAML) rather than as code?The text was updated successfully, but these errors were encountered: