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
It still uses the same LSP code analysis notifications for live updates as before.
It now routes through a mailbox to resolve concurrency issues .
The main handler is onTestsDiscoveredInCode
Hmm, when attaching to FSAC, I see that I get an exception from:
The test is found but I suspect the notification is not getting to the client.
@baronfel, shot in the dark: is FSharpSignatureData trying to resolve a symbol with cached checking information? As it is failing for newly typed code that would be my guess.
nojaf
linked a pull request
Apr 5, 2024
that will
close
this issue
Describe the bug
When adding a new unit test in an existing file, the new test does not get picked up.
Steps to reproduce
src\Fantomas.Core.Tests\Stroustrup\SynBindingFunctionExpressionTests.fs
[<Test>] let foo () = ()
Expected behaviour
The new test gets picked up.
Screenshots
Machine info
Additional context
I noticed @farlee2121 changed the way unit tests are detected in #1874. There no longer seems to be any notification coming from the LSP server.
Is the file being watched for changes? I can't really find any evidence for this in the current code.
The text was updated successfully, but these errors were encountered: