Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2023-04-12

Channels

#calva
<
2023-04-12
>
Dustin Getz13:04:54

Changing Calva: Definition Provider Property to prefer LSP does not commit, any ideas?

pez13:04:02

I think it might be the UI that is broken (or we are using it wrong, I should probably check that out). Anyway, see what the setting is in the JSON file. VS Code has commands for opening those files.

👀 2
Dustin Getz14:04:15

ok, here is the config after using the UI to set the property and then making sure to NOT blur the UI, instead directly closing the settings panel: 

"calva.definitionProviderPriority": [
        "lsp",
        "repl"
    ],

Dustin Getz14:04:30

so you're right that it seems to be a ui bug

pez14:04:41

Thanks for checking that. I shall wait with declaring it a UI bug until I have investigated it a bit more. It’s a very unfortunate glitch in any case.

Dustin Getz14:04:22

With this set, should I be able to code-nav into when-some without an attached REPL? (I cannot)

pez14:04:42

Yes, you should. Might be something up with your project config that clojure-lsp doesn’t like. Or it could be some corruption of its analysis cache. See restarting the clojure-lsp server helps. If not, stop it and delete .lsp/.cache and .clj-kondo/.cache, then start it again.

👀 2
Valentin Kostadinov20:04:40

Hello everyone, newbie here - both to Clojure and Calva. Calva Test-Runner question: I’m able to see all the tests in the Activity Bar (after enabling Calva Test Explorer), but they won’t run unless I have the corresponding editor open and loaded. Otherwise it just says: No tests found. 😱, ns: 0, vars: 0

pez20:04:19

Hi! Welcome to Calva!

pez20:04:23

It’s expected behaviour you see. The test runner is REPL based and it will only run tests that are loaded. You shouldn’t need to have the file opened, though. Once the test namespaces are loaded, tests in them will be run.

Valentin Kostadinov20:04:57

Thank you! Do I have to run the “Load/Evaluate…” command from every file with tests? Is there a way to load all test namespaces?

pez20:04:51

I don’t know what people do here. You could evaluate an ns form that requires all your test namespaces. Possibly clojure.test has some utility to find test namespaces so you can load them more dynamically. Let’s see if someone has some ideas around it.

Valentin Kostadinov20:04:01

I see. I’ll look around, At least I know I’m not overlooking something obvious! Thank you

🙏 2
pithyless09:04:29

cider-test has a cider-test-run-project-tests. I don't use it myself very often, but it is there. Theoretically, it should load all project namespaces? https://github.com/clojure-emacs/cider/blob/master/cider-test.el#L735-L741

pez20:04:51

I don’t know what people do here. You could evaluate an ns form that requires all your test namespaces. Possibly clojure.test has some utility to find test namespaces so you can load them more dynamically. Let’s see if someone has some ideas around it.

pez22:04:28

Dear Calva friends: Release v2.0.351: • https://github.com/BetterThanTomorrow/calva/issues/2154`repl-requires`https://github.com/BetterThanTomorrow/calva/issues/2154 • Bump bundled deps.clj to v1.11.1.1273 Adding a setting calva.autoReferReplUtilities, which you can set to • on-connect (default, giving you the repl utilities in the initial namespace), • always (in all namespaces you switch to), or • never (the command for doing this on demand is still there).