This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-12-28
Channels
- # adventofcode (6)
- # beginners (61)
- # boot (1)
- # chestnut (1)
- # cider (18)
- # cljs-dev (1)
- # cljsrn (3)
- # clojure (176)
- # clojure-android (8)
- # clojure-germany (12)
- # clojure-russia (4)
- # clojure-spec (7)
- # clojure-uk (5)
- # clojurescript (28)
- # css (10)
- # cursive (36)
- # datomic (7)
- # devcards (1)
- # docs (8)
- # emacs (17)
- # fulcro (29)
- # hoplon (28)
- # lein-figwheel (3)
- # leiningen (37)
- # lumo (1)
- # off-topic (54)
- # om (6)
- # re-frame (2)
- # reitit (7)
- # ring-swagger (23)
- # shadow-cljs (115)
- # sql (10)
- # uncomplicate (1)
- # unrepl (24)
Q: I have a dependency prone
whose jar contains generated JS that includes things like goog.object
. In Cursive, this means that goog.object
gets indexed twice, so function lookup requires a menu indirection for anything in core. This happened before with cljs-time
which contains an entire copy of clojurescript
for running tests, so I excluded it (inconvenient). Is there a better solution?
Trying something out with the Dependency Viewer, which I’d not properly apprehended before.
No, I don’t think that its “Remove From Scope” action does what I suspected.
Say, is there any way to see my exception stack traces in the Cursive repl?
@timgilbert Yes, when you receive an error there’s a button in the REPL menu bar, or you can bind the action to a key.
@briantrice I’ll have to sit down and look at that, I’m not sure off the top of my head.
Oh! Duh, should have noticed that. Thanks!
thanks!
@cfleming I tried using the result of “copy path” from the jar’s contents, as well as naming the directory segment, into project exclusions, but it didn’t help. Right now it seems like dependency indexing happens per-JAR.
this gist was certainly intriguing, at least: https://gist.github.com/johnnykang/eed464578e33f03cdc1b0d06c19c00e4
yeah… hard to maintain
I mean, I’m tempted to just clone and maintain branches of each offending library that omits the directory before packaging at this point, just so I can get F1 to call up cljs core signatures…
oh… IntelliJ thinks these are production classes. hmmm
or. library classes.
maybe I can make a special scope with the exclusions and use that to avoid indexing?
omg. Am I reading this right? People are publishing jars w/ their deps packaged in them?
yeah, I’ll file with the maintainer if I can express the problem right
especially if I can fix it with a PR
suggestions welcome: https://github.com/andrewmcveigh/cljs-time/blob/master/build.boot
just bumped from 0.5.0 to 0.5.2 in case it shakes that out…
:bump:
strangely enough, now cljs-time doesn’t have the test directory with clojurescript’s source in it. but prone still has the generated js. I’ll poke further, thank you.
ok, so generally it seems like when this happens, it’s fixable by using the “delete” option in the Project > Libraries panel, and then rebuilding while IntelliJ is closed (or invalidating caches)
I’m not sure how dependencies get compiled that way, but will try to keep an eye on the issue if it re-occurs.