This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (2)
- # beginners (150)
- # calva (59)
- # cider (10)
- # clj-kondo (63)
- # cljs-dev (15)
- # cljsrn (34)
- # clojure (127)
- # clojure-dev (16)
- # clojure-europe (12)
- # clojure-italy (18)
- # clojure-nl (6)
- # clojure-russia (3)
- # clojure-uk (23)
- # clojurescript (18)
- # clojutre (15)
- # clr (2)
- # crux (3)
- # cursive (3)
- # datomic (26)
- # duct (6)
- # fulcro (9)
- # graalvm (3)
- # joker (9)
- # lambdaisland (1)
- # off-topic (12)
- # om (1)
- # pathom (29)
- # re-frame (16)
- # reagent (2)
- # shadow-cljs (57)
- # slack-help (2)
- # spacemacs (45)
- # sql (20)
- # yada (3)
@harmmatan: You’re lookinng for resources on vscode extension development? It’s a bit lacking, I would say. The API docs are both good and bad. I can recommend joining the vscode dev slack and the extension channel there: https://vscode-dev-community.slack.com/messages/C74CB59NE
I was thinking about helping out Calva and taking some issues. Do you still think https://github.com/BetterThanTomorrow/calva/issues/89 is an easy one or do you have some other recommendations, Peter?
I don't think it is particularly easy, actually. But it would be awesome to have it done.
@janne.sauvala Oh, sorry, with your anon avatars I thought your question came from @harmmatan... and was about the issue he had mentioned. Confusion. So those compiler errors... might be a good first issue, actually.
Take a look at the test runner to see how we squiggle things there. And then it will be a matter of reading that
ex-data to pick up file path and line numbers and such. Might be that the biggest problem is figuring out when to clear the problem marks...
Slack apparently changed our avatars to be even more confusing 😄 I’ll take a look at that then, thanks!
I was using his example
(deftest foo (is (= (println 1) (println 2) (println 3) (println 4) (println 5))))
i don't think I'd want to see the printlns though, so I think this is behaving as I'd expect it to.
For me it prints:
Running test: foo… 1 2 3 4 5 1 tests finished, all passing 👍, ns: 1, vars: 1
@pez i've been doing some thinking about the whole REBL in Calva thing, since not everyone has REBL necessarily.
@gerred I think I have Calva Jack In working with REBL. Details are in this issue https://github.com/BetterThanTomorrow/calva/issues/240
Closed it and linked to the new page: https://github.com/BetterThanTomorrow/calva/wiki/Using-with-REBL Thanks for the help! Extra cool that the custom connect sequences could help with this, wouldn't you say, @UD8TU3HP0? 😄
it'd be nice to be able to configure (dunno if there's a ~/.clojure/deps.edn way to do this?) additional nrepl middleware in Calva
thinking about this issue: https://github.com/BetterThanTomorrow/calva/issues/240 and this project: https://github.com/RickMoynihan/nrebl.middleware
I think it should be a setting in Calva, a path to the REBL.jar and some way to choose if it should be included in the jack-in, then Calva injects everything that is needed. (Even if it looks like a huge dependency list for deps.edn…)
I need to either find some time to experiment with it or get a demo of how it works when it is set up manually. Then I might understand enough to know about how to do it and wether Calva should have some more support, beyond channeling evaluations like that.
hey side note, if you sign up for Github Actions, I'd happily port over my workflow that generates builds on every commit for the dev branch.
yeah I think there's a separate "evaluate and send to REBL" command as well. I have REBL starting up just fine, but that's the next step, thankfully @seancorfield has a great command for that over in his Atom setup with Chlorine, so I was able to at least spike it out and test it while jacked in.