nextflow-io / nextflow-io/language-server
Integrate futher nf-core restriction in language server
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 31
- Forks
- 8
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 2
Description
As we know now (I think so), nf-core conventions encompass the ones imposed by the language server, but do apply more restrictions. Under that, VSCode highlighting wil follow current Nextflow standards. But there isn't any ways to further restrict the language with, let's say, nf-core guidelines.
Please, add a configuration option (probably associated to a configuration file on the nf-core end) so we can apply extended community linting onto users modules and subworkflows that get submitted to libraries like nf-core or nf-neuro.
I know the nf-core/tools cli software is built to do such a review, but it's still not raising the errors on old DSL1 syntax (which may very well be non-nf-core-abiding synatx).
Contributor guide
No contributing guide indexed for this repository
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
The issue names the language server and nf-core/tools CLI but no files or tests. Start by comparing the language server's current restrictions with nf-core/tools review behavior, especially for old DSL1 syntax. Done means a configuration option can apply extended nf-core linting to submitted modules and subworkflows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, vscode
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100