This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-04-06
Channels
- # announcements (33)
- # babashka (13)
- # babashka-sci-dev (23)
- # beginners (94)
- # calva (105)
- # cider (37)
- # circleci (1)
- # clj-kondo (45)
- # cljs-dev (59)
- # cljsrn (2)
- # clojure (145)
- # clojure-czech (1)
- # clojure-europe (19)
- # clojure-nl (18)
- # clojure-norway (13)
- # clojure-portugal (1)
- # clojure-uk (5)
- # clojurescript (19)
- # community-development (2)
- # conjure (3)
- # copenhagen-clojurians (1)
- # core-async (34)
- # data-science (6)
- # datomic (25)
- # emacs (43)
- # fulcro (19)
- # graalvm (7)
- # graalvm-mobile (12)
- # graphql (10)
- # honeysql (3)
- # hyperfiddle (3)
- # improve-getting-started (2)
- # interop (20)
- # kaocha (3)
- # lsp (16)
- # meander (7)
- # off-topic (22)
- # other-languages (14)
- # portal (15)
- # releases (1)
- # rewrite-clj (2)
- # ring (1)
- # shadow-cljs (119)
- # spacemacs (19)
- # sql (65)
- # testing (4)
- # tools-deps (11)
- # xtdb (29)
@seancorfield are you using RCF? If so would you like to chat about your experience? We're doing a sprint on the next version of it right now. --- https://github.com/hyperfiddle/rcf/ Interested in anyone's experience report - please talk to us if you're using RCF, community is currently in #hyperfiddle
@U09K620SG No, I stopped trying to use it because of the named test issue I reported. I work extensively in the REPL and was relying on my fork of RCF with the changes I described in that issue -- but I stopped when y'all didn't seem very interested in my suggestions about named and unnamed test generation behaviors.
ty for the feedback!
I still think RCF is interesting but that issue is a complete showstopper for my workflow.