You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
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.
The text was updated successfully, but these errors were encountered: