rescript-lang / rescript-lang/rescript-vscode
LSP info messed up in JSX scope when there's an error
Open
Nobody has claimed this yet.
- Dominant language
- ReScript
- Stars
- 354
- Forks
- 63
- Avg merge
- 11h 29m
- Merged PRs (30d)
- 1
Description
When there's an error in the jsx scope, all the LSP data is messed up:
Once fixed, LSP gets back to normal:
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 file or test is named. Reproduce the problem in the VSCode plugin by introducing an error inside a JSX scope, then compare the LSP data with the corrected case shown in the report. Trace the language-server handling for that error state; done means LSP information remains correct while the JSX error is present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100