Fork me on GitHub
#calva
<
2019-11-25
>
ivana00:11:04

Thanks, I have upgraded VScode again, added needed files from lein template and it works as it should now.

vinai09:11:17

I’ve got a cljs test namespace, ans switched the cljs REPL to that namespace, too. When I run any of Calva: Run Tests for Current Namespace or Calva: Run all Tests I get the output > Running namespace tests… > > No tests found. What am I doing wrong?

vinai09:11:50

Also, what is the “best” way to restart the repl process if for example the clojure or clojurescript version dependency changed?

pez09:11:38

If you have jacked in, the easiest way to restart is to jack in again.

pez09:11:08

Is this shadow-cljs? @vinai

vinai09:11:44

No, this is a testing project created with lein new figwheel-main foo.core -- --reagent

vinai09:11:04

Just for getting familiar with Calva

vinai09:11:03

Restarting the repl - got it. Still trying to figure out how to run the tests 🙂

pez09:11:48

It might be that the test runner isn't working. I have had issues with it before.

vinai09:11:59

How can I confirm that?

pez09:11:12

I'll experiment a bit. brb

vinai09:11:05

Thank you very much

pez09:11:04

It doesn't work for me either. I need to check some what could be expected to work here. I know that it doesn't work with shadow-cljs, but I think it should with figwheel-main.

pez09:11:16

I'm sorry. Your first Calva experience fails here... I'm pretty sure the test runner should handle this. Please file an issue, and we'll look at it.

vinai09:11:43

Thank you very much for your help. I’ll open an issue

pez23:11:51

Dear Calva friends: I urgently need help testing the new Paredit. The whole effort was big to begin with, and have grown considerably during. Please see this PR and the specific comment for info on what and how to test it: https://github.com/BetterThanTomorrow/calva/pull/475#issuecomment-558380797 Many, many, thanks in advance for any help here! ❤️ ❤️ ❤️

🔨 1
calva 2
pez23:11:26

I’ll go unresponsive now, because I need to sleep. Cheers! 💤