-
Notifications
You must be signed in to change notification settings - Fork 51
Update and clarify SDRF and Json-Parameter parsing #596
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
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Note Other AI code review bot(s) detectedCodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review. ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
|
One suggestion I got is to parse the parameters from the SDRF file using an input schema. The samplesheet (SDRF) is parsed part of the To define which parameters are actually used in the end, the ones set in |
|
@ypriverol It is not really solved. I will need to add a section to the outputs descriptions where I highlight which parameters are picked up from the SDRF file (if provided). But otherwise the small updates can be merged |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR refactors the create_input_channel subworkflow to improve code formatting and modernize Groovy/Nextflow syntax. The changes focus on standardizing code style, replacing a class-based approach with a simpler map structure, and updating function call syntax.
- Replaced
Wrapperclass with a map-based structure for storing workflow state - Standardized formatting for conditionals, function calls, and assignments
- Added schema validation for "assay name" field in input JSON
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| subworkflows/local/create_input_channel/main.nf | Refactored workflow to use map instead of class, standardized code formatting with consistent spacing and parentheses for function calls |
| main.nf | Added explanatory comment about potential channel usage |
| assets/schema_input.json | Added "assay name" field validation to input schema |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
PR checklist
nf-core pipelines lint).nextflow run . -profile test_lfq,docker --outdir <OUTDIR>).nextflow run . -profile debug,test_lfq,docker --outdir <OUTDIR>).docs/output.mdis updated.Changes