jaredly / jaredly/reason-language-server
No go to reference for exceptions
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 649
- Forks
- 85
- PR merge metrics
- No merged PRs in 30d
Description
```reason
/* Example */
switch (result |> dataGet |> Json.Decode.list(Decode.repoProject)) {
| data => data
| exception (Json.Decode.DecodeError(msg)) =>
Js.log(msg);
[];
}
```
While hovering over / F12 over the symbol `DecodeError`, rls seems to not be able to tell that it is indeed exposed by the module `Json.Decode`, which is [defined here](https://github.com/glennsl/bs-json/blob/d545caf5547a0eef6b31812aa4c69ef3a5a882c8/src/Json_decode.mli#L16).
Contributor guide
No contributing guide indexed for this repository
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 Reason example and the Json.Decode.DecodeError symbol, then inspect the declaration in Json_decode.mli at the linked line. Reproduce hover or F12 on DecodeError; the issue is done when the language server resolves it to the declaration exposed by Json.Decode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- devtools, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100