Schema: Write future reference schema
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 322
- Forks
- 255
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 5
Description
We have plans for several extensions to the Nextflow parameter schema format.
To allow multiple groups to work in parallel, it would be good to manually write "the most complex schema possible" that we imagine supporting once those tasks are done. This way, we have a common reference point for where we expect to get to later in the year.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing Nextflow parameter schema format and any current schema definitions in the repository. Compare the planned extensions described in related issues with the present format, then define what the most complex future reference schema should contain and document the resulting reference point.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100