posit-dev / posit-dev/positron
Consider showing more (optional?) diagnostics for R code
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 184
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 206
Description
In https://github.com/posit-dev/positron/discussions/6574 @mynanshan points out that we don't have the full set of diagnostics like RStudio does:
The particular diagnostic that @mynanshan was looking for is "warn if no variable definition in scope", but there are a lot of these. Notice that these are individually configurable; I'm not sure if we want to go down that path for Positron.
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.
Research direction
No source files, tests, or entry points are named. Start with discussion 6574 and compare the diagnostic behavior shown in the linked screenshot with the RStudio diagnostics described there. Before implementation, clarify which diagnostics Positron should support and whether each should be configurable; done means the agreed diagnostics appear correctly in the R workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100