This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-27
Channels
- # admin-announcements (5)
- # cider (4)
- # cljs-dev (20)
- # cljsjs (2)
- # cljsrn (6)
- # clojure (126)
- # clojure-austin (2)
- # clojure-berlin (1)
- # clojure-brasil (5)
- # clojure-japan (1)
- # clojure-russia (14)
- # clojure-spec (2)
- # clojure-uk (3)
- # clojurescript (11)
- # cursive (19)
- # datomic (5)
- # editors (1)
- # emacs (10)
- # funcool (5)
- # hoplon (170)
- # instaparse (4)
- # jobs (1)
- # om (1)
- # onyx (1)
- # re-frame (14)
- # reagent (1)
- # testing (14)
- # yada (1)
Should breakpoints in java libs (closure-compiler) work? I tried adding breakpoints both to the decompiled class file and the source
Oh, maybe I just had the breakpoints set up in places before the error
Is there a way to type hint CLJS browser events such as:
(defn navigation [event]
(model/set-route! (.-token event)))
such that Cursive knows that .-token is the right thing?After unchecking the box, go to Settings->Plugins->Browse Repositories and hit refresh - does that help?
@juhoteperi: Yes, that should definitely work. Breakpoints can be occasionally flakey in Clojure but they’re very reliable in Java.
@timothypratley: No, unfortunately. However it looks like this might help in the near future (I’ll have to add Cursive support for it): http://clojurescript.org/reference/compile-time-type-checking
ooOOoo nice!
I’ve filed this to track it: https://github.com/cursive-ide/cursive/issues/1509
I can actually add that support independently of CLJS - it will just only help Cursive, not the compiler, until it works there.
That was not the easiest sentence to parse - what I mean is that Cursive can have that support for completion, symbol resolution etc even if the compiler doesn’t support it.
Ah I see that makes sense yup. Yeah it seems that there is growing support for Typescript from libraries out there. 🙂 Glad to hear there are some good options available. I'm actually really confused how Cursive manages to resolve so many JavaScript symbols, it sure makes it easier to know when all the externs etc are correct.
Yeah, I’m actually planning to go over all the CLJS resolution soon, since it’s very confusing and I can’t keep up with all the different things required to resolve symbols correctly. Once that’s more accurate hopefully the warnings will be more useful.
I’m actually going to have to bump https://github.com/cursive-ide/cursive/issues/1481 to the next beta build because of the subtleties involved.
Hahahaha totally. Yeah I can imagine that would be a doozy to handle 🙂