rescript-lang / rescript-lang/rescript-vscode
Errors from packages where no file is open don't appear on problems tab.
Nobody has claimed this yet.
- Dominant language
- ReScript
- Stars
- 354
- Forks
- 63
- Avg merge
- 11h 29m
- Merged PRs (30d)
- 1
Description
In a setup with at least one namespaced package, where I change something in the namespaced package, errors for a consuming package only appear on the problems tab when at least one file of the consuming package is open in VSCode.
I made a repository to demonstrate this behaviour: https://github.com/fhammerschmidt/rescript-vscode-problems-tab
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
Start with the linked reproducer repository and reproduce the issue in VSCode with a namespaced package and a consuming package. Trace how errors reach the Problems tab when no consuming-package file is open; done means those errors appear without opening a file in the consuming package.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100