This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-06
Channels
- # architecture (2)
- # aws (6)
- # bangalore-clj (3)
- # beginners (7)
- # boot (29)
- # cider (26)
- # cljs-dev (52)
- # cljsrn (1)
- # clojure (249)
- # clojure-dev (9)
- # clojure-italy (2)
- # clojure-norway (3)
- # clojure-russia (178)
- # clojure-uk (30)
- # clojureremote (6)
- # clojurescript (91)
- # core-async (4)
- # cursive (8)
- # datascript (3)
- # datavis (1)
- # datomic (6)
- # emacs (3)
- # figwheel (2)
- # hoplon (14)
- # incanter (6)
- # luminus (8)
- # mount (7)
- # off-topic (22)
- # om (25)
- # onyx (41)
- # pedestal (7)
- # re-frame (9)
- # ring (1)
- # spacemacs (4)
- # sql (1)
- # uncomplicate (1)
- # unrepl (37)
- # untangled (90)
- # yada (77)
Can Cursive leverage Intellij’s Javascript intelligence when using javascript interop? More specifically I’m using (js/require "realm")
and it would be great if cursive would understand that.
@vikeri Not right now, no. I’m also hesitant to build too much around that because it won’t work for anyone using the Community Edition. I am planning to make Cursive’s JS indexing smarter, though.
Hopefully at some point Cursive will be able to work in e.g. WebStorm, but that doesn’t work right now.
Okok, couldn’t one disable the x cannot be resolved
warning for javscript interop then?