-
-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stub files analyzing #2465
Comments
Adding context here from Slack from @ericdallo.
Slack thread: https://clojurians.slack.com/archives/CBE668G4R/p1676552690524579 |
@isacjunior do you opened that api.clj file at any moment? since that folder is not in the classpath, I would expect clojure-lsp to only report diagnostics if you manually open that file 🤔 |
@ericdallo no, I do not open that file. Just opening the VSCode and the problems in the terminal is shown. |
When a project is opened, the Calva is watching the stubs files
path/.lsp/.cache/stubs
and sending it to clojure-lsp to analyze and problems are shown on terminal. Interestingly, if the stub file noisy is opened and later close, the warning from VS Code fade away.The text was updated successfully, but these errors were encountered: