I will be a virtual attendant and am looking forward to it.

I’ll be there!

Im going

Myself and some of the Juxt/XTDB team will be there! Already had a few conversations with people here about electric

When the “plotly_click” e/fn handler is called on line 15 (new V1 …) , I get an invalid arity exception

What am I doing wrong?

I have a feeling that the proper way to do this is that the plotly callback should mutate some atom and then the electric fn should watch that atom

I think you can only call electric functions from within an electric function body or an e/def, and the problem is that plot! Is a regular cljs function and in it you are trying to call V!

Yes, you should call dom/on with an e/fn

What’s the story around interop? Plotly needs a plain javascript fn to handle its callback

oh, maybe i get it… instead of (.on div ….) use dom/on ?

I’ve updated the code to try dom/on . Now, I get a compiler warning Cannot infer target type in expression (. inst__30182__auto__ newPlot G__46562 G__46563) and it doesn’t seem that the callback is getting invoked at all.

Here’s a working version. The big realization for me is that new is a special form (hence all the electric macros). This approach relies on plain Clojurescript for the interop and state atoms to get reactivity with electric.

Adding a ^js type hint to js/Plotly where you call .newPlot may help with the warning. That shouldn't affect behavior in development but will probably break things when you try to compile with advanced optimizations

Thanks!

we have a convention to name electric functions capitalized. Electric functions are called with new . Therefore if you want to run electric code on a DOM event you call

(dom/on div "plotly_click" (e/fn [data] ... (new V! ...)))

(dom/on! div "plotly_click" (fn [data] ...))