Closed danielneal closed 6 years ago
I'm not opposed to using cljs-oops
(which I personally use too). If this is going to break in production then I think we should do something (maybe use goog.object
?).
I can confirm that it also fixes #55
Rad. Great work. Thanks for digging into this!
I think this should fix #58 (and therefore resolve #46)
I'm not sure about calling
.registerRootComponent
in advanced builds, though, there might be an externs problem.I usually use
ocall
fromcljs-oops
to circumvent this, but I didn't want to import a library to the template unnecessarily.