nextflow-io / nextflow-io/language-server
Ability to ignore warnings per line
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 31
- Forks
- 8
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 2
Description
The language server reports a range of code test results. Some are pretty critical (errors / deprecations) but some are a bit my stylistic (eg. unused variables needing a leading underscore).
It would be good if the more opinionated / less critical could be selectively ignored by using inline comments.
In the Python world this is typically done using # noqa comments - see the Flake8 docs. A specific error code can also be specified to ignore only that one. The exception typically only applies for the single line of code.
In Nextflow we could apply a similar // noqa comment to ignore a linting warning.
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
No files or tests are named. Start by tracing how the language server produces and publishes code-test diagnostics, then review how inline comments could identify ignored warnings or specific error codes. Done means a Nextflow // noqa comment suppresses the intended warning for its line without hiding more critical diagnostics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100