Problems go stale about vscode-reasonml

Thanks for the feedback.

Often problems picked up by merlin in one file is fixed by altering a different file, but this isn't picked up so the problems go stale.

If I understand correctly what you are describing this might be hard to fix just due to how merlin itself operates. Merlin only provides feedback when you synchronize edits from the buffer for a particular file. It's not project based in a more general sense and is somewhat limited in what it will report. So if file B reports a problem due to an issue in file A, and then you go fix the issue in file A, merlin won't automatically refresh the feedback for file B.

One possibility might be to try and figure this out somehow on the editor side and then force merlin to do the refreshes for associated files automatically. But I'm not sure if that's a good idea. It would require adding some complicated logic that would likely be fragile and not always work as expected.

Another possibility might be to allow the option of building the project in the background between edits or saves (probably only saves) and using that to override what merlin reports if the feedback is different.

This is particularly annoying if you delete a file that had problems associated with it. Then you're pretty much screwed and have to restart vscode to fix it.

Is this in a scenario where the file you are deleting was previously opened in the editor? In that case, when you delete the file, I would have thought the problems associated with it would disappear when editor for the file is closed just prior to deletion.

[glennsl]

Another possibility might be to allow the option of building the project in the background between edits or saves (probably only saves) and using that to override what merlin reports if the feedback is different.

I actually do have a build task set up in tasks.json, and I think defining a problemWatcher on that instead of using merlin for problems would do the trick. But I also think this needs to be set up (semi-)manually per project, which is a bit inconvenient.

I would have thought the problems associated with it would disappear when editor for the file is closed just prior to deletion.

That would make sense. Unfortunately it does not, and they don't seem to think it's their problem to fix: microsoft/vscode#23010