rescript-lang / rescript-lang/rescript

Warnings in the watch mode

Open
#8,158 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
OCaml
Stars
7.5k
Forks
485
Avg merge
1d 2h
Merged PRs (30d)
55

Description

I have N warnings in the app. I run rescript watch - it shows all of them and editor integration shows all of them as well. Then I save some file in the editor, and all of the warnings disappear from diagnostics.

This is what I see in the console:

Image

After each consequent save, compiler stops outputting warnings - I guess it's related to the reason they disappear from editor diagnostics?


Also, two kinda unrelated remarks:

  1. Feedback time - from save to update - noticeably increased compared to v11. Is this expected or is it something with my setup?
  2. Seems like if I have 3 packages in a workspace, each package has own namespace in editor integration? With Rewatch, I hoped to get workspace wide diagnostics as it's done in rust-analyzer, but apparently it's not how it works in ReScript LSP?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the behavior with rescript watch, saving a file after warnings appear, and checking the editor diagnostics. The payload names no source files or tests, so trace the watch-mode compiler output and editor integration first. Done should preserve warnings after subsequent saves and clarify the feedback-time and multi-package workspace behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
ocaml
Domain
compilers, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.