This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (24)
- # beginners (80)
- # cider (18)
- # cljs-dev (12)
- # clojure (94)
- # clojure-berlin (15)
- # clojure-dev (10)
- # clojure-gamedev (3)
- # clojure-italy (38)
- # clojure-japan (4)
- # clojure-russia (109)
- # clojure-sg (1)
- # clojurescript (161)
- # code-reviews (29)
- # core-async (17)
- # datomic (20)
- # editors (14)
- # instaparse (17)
- # ldnclj (9)
- # off-topic (9)
- # om (2)
- # onyx (2)
- # re-frame (11)
- # reagent (46)
Can't see how it will have anything to the value or type or name
It will be because the namespace, in which the handler is registered, is not
Unless you actively require that namespace somewhere, the cljs dependency mechanism won't know it has to be loaded. And if it isn't loaded, then the registration won't be made. And then later when you
dispatch, you'll be told the handler was never registered
Hmm. I've required that namespace,
handlers.cljs, in my
core.cljs for that reason. And all the other handlers (written identically) are working well.
core.cljs get required for tests? (In order for it to trigger
(.log js/console "here") in
handler.cljs to be sure?
I'm hammering away at this because your symptoms perfectly match somehow never registering the handler.
And any thoughts that this being related to a type or name don't seem to make sense
I appreciate your hammering away! Any information is great.
Now that you mention it,
lein test just runs Clojure tests, and gives that warning.
lein cljsbuild test runs my ClojureScript test - and I'm directly testing that handler with no issues.
Also, that's the handler I most recently wrote. So perhaps the Clojure side just hasn't gotten with the program yet?