This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-03
Channels
- # admin-announcements (2)
- # alda (4)
- # beginners (15)
- # boot (89)
- # cljs-dev (88)
- # cljsrn (75)
- # clojure (149)
- # clojure-belgium (16)
- # clojure-france (2)
- # clojure-greece (6)
- # clojure-russia (108)
- # clojure-spec (39)
- # clojure-taiwan (3)
- # clojure-uk (7)
- # clojurescript (70)
- # css (3)
- # cursive (17)
- # data-science (2)
- # datascript (7)
- # datomic (41)
- # dirac (3)
- # hoplon (12)
- # instaparse (1)
- # juxt (3)
- # lambdaisland (9)
- # mount (4)
- # off-topic (6)
- # om (71)
- # om-next (4)
- # onyx (22)
- # other-languages (56)
- # perun (15)
- # proton (6)
- # re-frame (32)
- # reagent (42)
- # specter (34)
- # spirituality-ethics (7)
- # tmp-json-parsing (5)
- # untangled (13)
- # vim (4)
- # yada (6)
is it possible to set the default for “New clojure namespace” to be ClojureScript instead of Clojure ?
@danielcompton: thanks!
Installing Java 6 to try stop the IntelliJ crashing 😞
Is it a known bug that Rum macros are still not getting resolved? I don't see an issue for it on Github.
@darwin: I am not referring the macro. I am doing:
(require '[rum.core :as rum])
(rum/defc ...)
Is this what you are doing?@kenny: when I do (:require-macros [rum.core :as rum-core])
and then rum-core/defc
it works as expected
looks like the only problematic case is yours, when is it ambiguous what namespace are you referring to, if cljs rum.core or clj rum.core
I agree that it should get fixed if it is recognised as valid clojurescript resolution (I have fuzzy knowledge about auto-importing macros via shadowed namespace naming)