Expand gget/gget into different subtools like gget/blast, gget/ref ...
Open
Nobody has claimed this yet.
new module
wishlist
- Dominant language
- Nextflow
- Stars
- 429
- Forks
- 1.1k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 153
Description
I'm not quite convinced that we should have a general wrapper for gget as it is now...
We might need to expand it into different subtools gget/blast, gget/ref, ...
But this would be a big change outside the scope of this nf-test migration 😉
Originally posted by @LouisLeNezet in https://github.com/nf-core/modules/pull/8518#pullrequestreview-2868697804
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 reading the discussion quoted from pull request #8518 and inspect how the current gget wrapper is organized. Clarify which subtools are intended and how the migration scope should change; done requires an agreed design before implementation begins.
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
- 20/100