-
Notifications
You must be signed in to change notification settings - Fork 178
Description
Describe the bug
We're seeing an issue now in the LSP where certain actions can reliably cause the LSP backend to stop responding. The culprit is unwrap calls, which should only be present in tests not library or binary code.
To Reproduce
I can reliably get the native LSP (in zed in my, but probably emac as well) to stop working under certain conditions. On main (and I suppose on the release version as well)
For example, removing a closing ) and saving the file will cause the lsp to stop sending diagnostics
Steps to reproduce the behavior:
- Open a clarity contract in a LSP enabled editor
- Remove a closing paren
- Save the file
- See error
Expected behavior
The editor should display a diagnostic about the missing paren, and continue responding normally to LSP notifications
Screenshots
Environment (please complete the following information):
All editors on all platforms, with current main and probably all previous versions
Additional context