posit-dev / posit-dev/positron
Should PROBLEMS be displayed from an untitled file?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 184
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 206
Description
Here I am in the source of an R package, but I have some code in Untitled-3 that I'm fiddling around with (it's copy/pasted from some R code inside ark). It feels like PROBLEMS shouldn't scrutinize the contents of Untitled-3 the same way that it does actual files within the project.
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
Reproduce the report in Positron with an R package open and code entered in Untitled-3, then compare the PROBLEMS view with diagnostics from an actual project file. Trace the existing PROBLEMS and untitled-editor behavior to identify where diagnostics are collected. Done means Untitled-3 is not scrutinized like a project file while real project diagnostics remain visible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r, typescript
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100