Chris Kipp

I think that now there is a neotest extension and we also have a built-in test explorer now via https://github.com/scalameta/nvim-metals/pull/474 we should be good to close this. We can definitely...

Is this still being worked on, or are you waiting for another review @nicolasstucki? Just wanting to know if I should mark this as a draft or not.

Hey @Linyxus are you willing to give this a rebase? If so, I think we can try and get this reviewed.

Testing this is no longer an issue and is closed as of https://github.com/lampepfl/dotty/pull/16882. Since the example here contains an external library and the original PR does have a test illustrating...

Going to mark this as a draft for now. If you dive back into this, please do mark it back as ready to review!

> Hello everyone, any progress? If not, I will have to continue using the jb's IDEA. If there aren't any updates in here, it's safe to assume there isn't any...

Note that in nightly this isn't an issue, so there is something funky going on with the latest stable version of Nvim that is impacting this. I'll leave this open...

In the example video though there wasn't a single change in any sources. So even in that scenario no matter what compilations are triggered? I believe in Bloop these would...

> Yes, every time build target in focus is changed. Gotcha, didn't catch that before, but makes sense. > add delay to status, so quick compilations are not shown, No,...

So I was playing around with this again today because I noticed in a minimal hello-world scala-cli project I was getting a bunch of duplicates. I've included the LSP logs...