Control auto-refresh with config option about neo-tree-diagnostics.nvim

[cseickel]

So far so good. I really like the "there are x unprocessed" message, that's a nice touch. I'll keep using it throughout the work day and let you know how it works out.

[mrbjarksen]

I'd be happy to add a config option for this, although I'm more worried about the performance. How many diagnostics can the source handle before freezing, and how long is the delay? Maybe making the refresh function async would be worth the effort?

I'll add an option in the meantime, at any rate. I'm thinking refresh_delay for the debounce and refresh_event to adjust when it fires.

[cseickel]

How many diagnostics can the source handle before freezing

That's a good question! I don't really know because it's frozen. I had also thought about adding a limit for the number of diagnostics, like if there are more than 100 or 1,000, just bail out with a warning.

The type of thing that could cause the problem is changing a core data provider class that is used throughout the project in a way that breaks it in typescript. I just did that as a test and it produced 263 errors. I'm guessing there is a problem where as I'm typing, it's producing 263 errors on every keystroke. Or maybe I did something that produced more with a certain edit. 🤷🏼

[mrbjarksen]

@cseickel I just added the options refresh.delay, refresh.event and refresh.max_items on the branch refresh-config. Can you confirm this works as expected before I merge?

[cseickel]

I think it works perfectly, I'd say it's good for release. 🚀

Thanks!

[mrbjarksen]

Great, thanks!