w0rp

Have a look at the CI results. You can run the checks locally. Check `:help ale-dev`. The Vim text documentation needs to match the Markdown documentation.

Not for version 4.0.0, but remind me in a year.

I would like to fix this, but I'm not sure how to fix it.

I'll have a think about this. ESLint keeps changing over the years and this change could break something.

This looks like the correct behaviour to me. You'll have to fix the tests. See `:help ale-dev`.

FYI @hsanson

I tried this again, but Windows tests in GitHub actions are just far, far too slow. I gave up after waiting for twice the speed at which AppVeyor builds for...

Ahh, I understand what you mean now! An initial change just to debounce sending a change for a buffer is pretty easy to do. We can just stop-start a timer...

More specifically, the difficulty in sending only the range of bytes that have changed in a file is that you have to answer two difficult to answer questions. 1. How...

I'm likely to do the "just debounce changes" part in the milestone, and move the "only send what has changed" part out of the milestone and into another issue.