wiki: suggestion and typo
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 70/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- r
- Domain
- documentation
Research direction
Open the R-Language-Service wiki page and review its Diagnostics and Formatting sections plus the table of contents. Add the lintr description and link, update the diagnostics wording, and remove the duplicated “through the” in the styler sentence. Done means both wiki sections and their table-of-contents entries match the wording requested.
Written by the indexing model from the issue text.
Description
The Diagnostics section should mention lintr, e.g.:
The language server provides code diagnostics through the [lintr](https://lintr.r-lib.org/) package in R. See [here](https://github.com/REditorSupport/vscode-R/wiki/Code-linting) for configuration.
and in the table of content:
-[Diagnose potential errors and unreliable code](https://github.com/REditorSupport/vscode-R/wiki/R-Language-Service#diagnostics)
+[Diagnose with `lintr` potential errors and unreliable code](https://github.com/REditorSupport/vscode-R/wiki/R-Language-Service#diagnostics)
(same wording as for the reference to styler in the Formatting section and table of content)
There is a typo in the Formatting section:
-The language server provides code formatting through the through the [styler](https://github.com/r-lib/styler) package in R. See [here](https://github.com/REditorSupport/languageserver#customizing-formatting-style) for configuration.
+The language server provides code formatting through the [styler](https://github.com/r-lib/styler) package in R. See [here](https://github.com/REditorSupport/languageserver#customizing-formatting-style) for configuration.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 139
- Avg merge
- 10h 1m
- Merged PRs (30d)
- 7
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.
More from REditorSupport/vscode-R
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
REditorSupport/vscode-R#1687 · 4 comments · 3 reactions ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
REditorSupport/vscode-R#1641 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
REditorSupport/vscode-R#1740 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
REditorSupport/vscode-R#1732 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
REditorSupport/vscode-R#1727 · 23 comments ·
All issues in REditorSupport/vscode-R
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·