It's one-directional, jvm->vis

You can use observable view to drive updates, see example in vlaaad.reveal/vega-view docstring

My concern with making it 2 directional is that serialization now also has to work 2 way, and it will bring complexity where e.g. map vals are keywords in JVM, then that are serialized to strings when converted to json, so you receive something else back

Can you describe the usecase for 2-directional signals communication?

i’m displaying flamegraphs of the running repl code through vega. when you click on a trace i’d like to know in clojure so i can jump the ide to that function def, rerun that function or show a detailed view for arguments/return values. i’ve got a prototype in portal already, just didn’t have the time to finish yet, would be interesting to also get it working with reveal. the more general usecase would be user interaction for data reload/streaming

Ah makes sense. I'll see what I can do

I'm working on signal listeners now