This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-03-01
Channels
- # announcements (2)
- # architecture (8)
- # babashka (21)
- # beginners (75)
- # calva (3)
- # clj-kondo (6)
- # cljdoc (6)
- # cljs-dev (10)
- # clojars (4)
- # clojure (94)
- # clojure-europe (12)
- # clojure-nl (4)
- # clojure-norway (3)
- # clojure-spec (6)
- # clojure-uk (4)
- # clojurescript (51)
- # community-development (13)
- # core-async (3)
- # css (1)
- # cursive (8)
- # datomic (7)
- # girouette (3)
- # graphql (3)
- # improve-getting-started (4)
- # integrant (2)
- # interop (5)
- # jobs (12)
- # kaocha (1)
- # lsp (24)
- # malli (4)
- # membrane (13)
- # nextjournal (9)
- # off-topic (6)
- # re-frame (9)
- # reitit (2)
- # remote-jobs (1)
- # reveal (4)
- # ring (4)
- # scittle (3)
- # shadow-cljs (4)
- # spacemacs (1)
- # testing (2)
- # vrac (1)
Is there something special I have to do, to get vars resolved in a top-level deps tool file? I have a top-level build.clj
file, and build
is checked as a “Tool Alias” in the Clojure Deps tool window. Is there more to do to get Cursive to resolve, or is something wrong with my setup?
I found the way Cursive achieves this to be a little flakey at an IntelliJ level. If you close your project and re-open it, does that fix it?
(it’s not required to completely shut down the IDE to test this, just close the project, although completely restarting is one way to achieve it).
I've experienced this too, closing and reopening the project (mostly) seems to fix it, and then project seems to stay OK.
Yes, that’s been my experience too. I suspect that it might still be flakey when adding new deps, for example, but I don’t do that often enough to be sure.
Closing/reopening didn’t help. I could try deleting the IDEA files/dirs and reimporting. I’m not sure if it’s related, but it wasn’t even identified as a deps.edn project at first. I was tearing my hair out for a while trying to locate the tools.deps window, but cycling the power fixed that, at least.