@nrako have any events been dispatched while the panel was open? It won't register the events when it is closed.

is seems like it’s not necessary in re_frame for any reg-event-* to have the signature [db/cfx event].. how is that handled? i found https://github.com/Day8/re-frame/blob/17e1637f310243cab47b5900e1c4674d131db653/src/re_frame/std_interceptors.cljc#L110 which is the invoker, but i don’t get why the compiler doesn’t complain if you declare a handler with a fn signature of 1 instead of 2

@lwhorton that’s a cljs thing I believe

((fn [x] x) 1)
;;= 1

((fn [x] x) 1 2)
;;= 1

no warnings from a cljs repl

which I believe is a consequence of cljs mirroring JavaScript function calling, which allows that.

ah so if it’s an unnamed fn it looks like the compiler doesn’t enforce it

and somehow underneath it’s getting applied which handles the multi arity, i bet

You can call JS functions with too many args, and it ignores them

So CLJS is probably compiling to similar normal JS functions

(there are some other things involved, but down at the bottom)

I won’t say it with 100% certainty because I didn’t read the relevant impl, but I believe this is the case

you are correct that it looks like if I call a named defn fn in CLJS with the wrong arity, it will give a warning

So your link to re-frame.std-interceptors/db-handler->interceptor is a higher-order function that calls the handler - so no warnings, whether your handler is a named or anonymous fn

kind of annoying… but i’m already deep in a macro so what’s one more gotchya 🙂

Well, it isn’t re-frame specific at least 😛 have to embrace the chaotic world of JS