rescript-lang / rescript-lang/rescript-vscode
Integrate reanalyze into the LSP so more editors can benefit out-of-the-box
Nobody has claimed this yet.
- Dominant language
- ReScript
- Stars
- 354
- Forks
- 63
- Avg merge
- 11h 29m
- Merged PRs (30d)
- 1
Description
Similar issue to: https://github.com/rescript-lang/rescript-vscode/issues/1108
My understanding from reading forums is that currently the excellent reanalyze tool is not integrated into the lsp, but is a separate tool that can either be invoked directly by the vscode plugin or from the rescript-tools cli.
If this could be integrated into the LSP, users like myself who don't use vscode could directly benefit from these tools without having to use vscode. I personally use Emacs, but lsp seems to be the best way to ensure cross-editor compatibility.
I could also work on parsing the output of the cli tool in the emacs mode but this could be a little cumbersome/error prone.
Happy to look into this myself is someone points me in the right direction.
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 by reading the related rescript-vscode issue 1108 and tracing how the VSCode plugin or rescript-tools CLI currently invokes reanalyze. Determine where the LSP integration belongs and how reanalyze results should be exposed, then verify that a non-VSCode LSP client can benefit from them.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100