This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-18
Channels
- # announcements (17)
- # babashka (109)
- # beginners (212)
- # calva (1)
- # chlorine-clover (7)
- # cider (8)
- # clj-kondo (31)
- # cljsrn (2)
- # clojure (33)
- # clojure-dusseldorf (1)
- # clojure-finland (2)
- # clojure-france (22)
- # clojure-germany (1)
- # clojure-losangeles (1)
- # clojure-spec (6)
- # clojure-uk (19)
- # clojurescript (31)
- # conjure (41)
- # cryogen (1)
- # data-science (11)
- # datomic (6)
- # emacs (5)
- # exercism (8)
- # figwheel-main (2)
- # fulcro (57)
- # graalvm (15)
- # hoplon (15)
- # jobs-discuss (32)
- # kaocha (7)
- # off-topic (14)
- # pathom (2)
- # planck (9)
- # quil (1)
- # rum (5)
- # shadow-cljs (34)
- # spacemacs (33)
- # tools-deps (1)
- # xtdb (9)
@olical I fixed the ns
resulting in multiple results issue in 2.8.97
. you mentioned something else related to in-ns
?
Oh in-ns wasn't working unless it was top level which did work on other repls but that's a non issue. Thank you so much for the quick fix. I'll have a play about and make sure everything is in order now.
how did you use in-ns
? that should really only work at the top-level in other CLJS REPLs too?
clj -m cljs.main -r
ClojureScript 1.10.520
cljs.user=> (do (in-ns 'cljs.core) ::foo)
WARNING: Use of undeclared Var cljs.user/in-ns at line 1 <cljs repl>
Execution error (Error) at (<cljs repl>:1).
Cannot read property 'call' of undefined
Wondering if I should use ns or in-ns since I think in-ns to something that hasn't been defined yet causes weird issues :thinking_face:
well in the case of shadow-cljs you can just send :ns
as part of the nrepl message to ensure the namespace things get eval'd in
https://github.com/nrepl/nrepl/blob/master/src/clojure/nrepl/middleware/interruptible_eval.clj#L63
Ah so :ns
does work on eval, just undocumented. Buuuut it won't let you set it to a namespace that isn't defined yet, so you'd have to do a little dance of "oh it didn't work, eval (ns ...) then try again"
Also because Conjure reconnects to ongoing sessions by default, if I lose connection to a CLJS REPL and reconnect it will still be CLJS, I won't have to jack in again.
How detailed would you like your test output :thinking_face: would you like to know each namespace and var that passed / failed on individual lines? Or just failures.
Implemented testing through CIDER today but didn't test it with CLJS until I was done, oops. It doesn't work which is understandable, CLJS testing is very different. Might just roll back a day though 😅
The original code was suuuuper simple and just relied on Clojure's stdout of test results.
Git reverted. If CIDER adds cljs support to the testing operations I'll just dig that commit back out.
I don't want to end the day without adding a feature so I'm adding fully configurable namespace refreshing.
Done. Damn Aniseed and the framework I've built make this pretty simple 😄 <localleader>rr
refreshes changed, ra
refreshes all, rc
clears the cache. All mappings configurable and optional config options available to provide a before
, after
and dirs
option.