Push diagnostics after didChange don't appear to be debounced

[NoTuxNoBux]

Hello

This language server is used by the Zed Groovy plugin, in which we found an issue where in Jenkinsfiles, typing a few characters in rapid succession results in each of those typing actions having diagnostics calculated, rather than once for the entire 'commit'.

In other words, the diagnostics calculation doesn't appear to be debounced after didChange is sent by the client, resulting in the client seemingly playing catchup (see also the linked ticket).

Perhaps there is some configuration that can change the way this works and it's just a default that isn't optimal, but I couldn't easily find language server parameter documentation for the Groovy language server.

[joshtynjala]

Interesting. I guess that I didn't realize that language servers typically debounce diagnostics checking from didChange. However, I just tested TypeScript in VSCode, and I can definitely type really fast for a long time, and new diagnostics aren't reported until I stop typing.