rescript-lang / rescript-lang/rescript-vscode
[feature request] support going to type definition with not saving the code.
Nobody has claimed this yet.
- Dominant language
- ReScript
- Stars
- 354
- Forks
- 63
- Avg merge
- 11h 29m
- Merged PRs (30d)
- 1
Description
As you can see in the screen shot, the code is not saved, but we can get the type tips for function Recoil.atom, this is great for us to look up the usage of it. But i also want to know what type the function's paramter accept, for now, i only know the type called atomConfig<'value>, could our editor support going to the atomConfig<'value>'s definition? I know that if i save the code and make the code context correct, i can go to the position of it's definition, but this would taking a lot of time.
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 reproducing the ReScript VSCode plugin behavior with an unsaved call to Recoil.atom and inspect how type tips and go-to-definition currently work. Done means the editor can navigate from the parameter type atomConfig<'value'> to its definition without requiring the code to be saved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100