You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 12, 2022. It is now read-only.
Although the API has exposed an option to enable diagnostics, I find that the results might need some improvements. Too often I see the LS report no issue with syntactically incorrect snippets. This can confuse users, and to some extent, decreases the user trust in the LS. When the false positive rate goes below some threshold, the end user might just choose to turn it off for good.
Is the diagnostics feature still of "experimental" level of quality, as opposed to "production"? What's on the roadmap for diagnostics?
Thanks!
The text was updated successfully, but these errors were encountered:
Diagnostics is experimental. Our roadmap is currently frozen since the Go Tools team will be releasing an official LSP server soon. In the meantime you should consider trying out https://github.com/saibing/bingo/
Although the API has exposed an option to enable diagnostics, I find that the results might need some improvements. Too often I see the LS report no issue with syntactically incorrect snippets. This can confuse users, and to some extent, decreases the user trust in the LS. When the false positive rate goes below some threshold, the end user might just choose to turn it off for good.
Is the diagnostics feature still of "experimental" level of quality, as opposed to "production"? What's on the roadmap for diagnostics?
Thanks!
The text was updated successfully, but these errors were encountered: