This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-05
Channels
- # adventofcode (8)
- # aleph (42)
- # announcements (4)
- # beginners (157)
- # boot (4)
- # calva (1)
- # cider (6)
- # cljdoc (8)
- # cljs-dev (1)
- # cljsrn (3)
- # clojure (50)
- # clojure-europe (9)
- # clojure-italy (16)
- # clojure-nl (2)
- # clojure-russia (6)
- # clojure-spec (59)
- # clojure-uk (25)
- # clojurescript (20)
- # core-async (41)
- # cursive (30)
- # data-science (9)
- # datomic (20)
- # fulcro (28)
- # kaocha (9)
- # nrepl (1)
- # off-topic (3)
- # om (3)
- # pathom (10)
- # re-frame (8)
- # reagent (2)
- # ring-swagger (38)
- # rum (9)
- # shadow-cljs (209)
- # spacemacs (7)
- # tools-deps (11)
- # vim (6)
- # yada (2)
For some reason, when the intellij light bulb icon appears on >defn
from [ghostwheel.core :as gw :refer [>defn]])
it does not resolve it to the ghostwheel definition
Does anybody know how cursive / intellj auto detect new libraries in the classpath for this?
@pvillegas12 What do you mean by “does not resolve it to the ghostwheel definition”? What are you seeing?
having required [ghostwheel.core :as gw :refer [>defn]])
it is a macro which is similar to defn
I want intellij to basically treat it as a defn
Yes, but how is it actually defined - is it defined using defmacro
or some other macro?
defmacro yes
I might be lost on how to make intellij load dependencies
(so that it knows how to resolve these with the lightbulb I was referring to)
yes, looks like intellij knows about ghostwheel but cannot recognize the macro >defn
(even when requiring it)
@pvillegas12 Which version of ghostwheel are you using?
gnl/ghostwheel {:mvn/version "0.3.5"}
using deps.edn
, how do I trigger cursive to load that into the classpath?
You can do that from the deps toolwindow, View->Tool Windows->Clojure Deps, then press the refresh button.
hmmm, that does not help with my problem
I’m not seeing https://cursive-ide.com/userguide/macros.html behavior is what I’m guessing
hmm, also getting weird behavior with spec, getting s/cat can be required
If you open File->Project Structure, then select Modules and select your module, under Dependencies do you see gnl/ghostwheel there?
got it working @cfleming
thanks for pointing me in the right direction, I forgot the (:require
form…