Is that expected out of the box? 👆

I don't remember boot-reload + boot-hoplon doing that before.

It's appending the same element updated instead of replacing it.

@mynomoto: i remember introducing that sort of regression with reload when i was working on the singleton constructors some time ago. what version of hoplon are you using?

@jumblerg : [hoplon/hoplon "6.0.0-alpha16"] and [hoplon/boot-hoplon "0.3.0"]

@mynomoto: is there any chance this is something you built from master after the 6.0.0-alpha16 distribution?

@jumblerg not really, it has been ages since I did a install from hoplon source. Can't you reproduce?

i was concerned it was being caused by my most recent modifications to the merge-kids fn. i haven't seen this issue in a while; might want to try master and 0.3.0-SNAPSHOT, which i'm using with boot-reload.

i'm using boot-reload 0.4.12, btw. 0.4.13 breaks advanced optimizations.

You mean if you use boot-reload and advanced optimizations at the same time?

So hoplon master and boot-hoplon 0.3.0-SNAPSHOT? 0.3.0 is released, is it not good?

yes, when i'm testing during development, e.g. boot develop -o advanced:

(deftask develop
  [o optimizations OPT kw "Optimizations to pass the cljs compiler."]
  (let [o (or optimizations :none)]
    (comp (watch) (speak) (hoplon) (reload) (cljs :optimizations o) (serve))))

It's a rare occasion when I run with any optimizations when doing dev but I know this pain.

i typically don't, but there are times it is helpful, such as when i'm importing libraries or trying to identify issues with externs.

Yeah, externs are usually my reason 😕

Same thing with hoplon master and 0.3.0 snapshot or not.