Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support different input schema's for different demultiplexers #138

Open
edmundmiller opened this issue Aug 22, 2023 · 1 comment
Open

Support different input schema's for different demultiplexers #138

edmundmiller opened this issue Aug 22, 2023 · 1 comment
Labels
enhancement Improvement for existing functionality

Comments

@edmundmiller
Copy link
Collaborator

Description of feature

Need to work out the required part.

I wonder if we can have different schemas depending on the demultiplexer?
@edmundmiller edmundmiller added the enhancement Improvement for existing functionality label Aug 22, 2023
edmundmiller added a commit that referenced this issue Aug 22, 2023
@edmundmiller
fix: Update input schema
21dad4b 
Need to work out the required part. I wonder if we can have different
schemas depending on the demultiplexer.

#138
@edmundmiller
Copy link
Collaborator Author

Looks like it's gonna work!

Channel.fromSamplesheet(
  'input',
  schema_filename: 'custom_nextflow_schema.json',
  skip_duplicate_check: false
)

This was referenced Aug 23, 2023
Merged
Open
@grst grst mentioned this issue Aug 7, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Improvement for existing functionality
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@edmundmiller