REditorSupport / REditorSupport/languageserver

too many lintr warnings

Open
#668 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
R
Stars
675
Forks
118
Avg merge
1d 37m
Merged PRs (30d)
11

Description

Too many miniscule and almost meaningless errors are raised by default on the languageserve package,, specially the VS Code extension and implementation of the lintr package. Perhaps some communication between lintr and languageserver to create a better default? Styling package could also be doing it's part in the ammount of warnings and flags raised by default.

Info:

vs-codeR: Less aggressive linting #1400

lintr documentation regarding the languageserver defaults

Checked open and closed issues here regardig the linter and mostly found people commenting on trying to remove them/getting errors while trying to edit the defaults:

Disable Lintr but keep other diagnostic errors #456
.lintr defaults are not respected #235

Or people nitpicking the warnings:

Formatting and linting are inconsistent in terms of spacing a^(b) #273

This is a relatively minor QoL issue, but fixing it would allow for less fidgetting with the defaults by the users, and thus hopefully less issues.

This issue was also raised in the lintr package repo.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the languageserver and lintr default behavior described in the linked lintr documentation, then review the referenced VS Code and languageserver issues. Determine which package owns the diagnostic defaults and agree on a less aggressive configuration. Done means the default warnings are reduced consistently without requiring users to edit their settings.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.