@tony.kay I'm looking through untangled-components right now and this is really nice! Thanks for sharing.
But I was wondering any plans/desires to make these components cljc compatible so they can be rendered on the server?
Having super fast initial load times would be really nice.
Has anyone else tried to update to ClojureScript "1.9.293" on a untangled-template project? I get clojure.lang.ExceptionInfo: failed compiling file:resources/public/js/compiled/dev/untangled/client/data_fetch.cljs.
@grant: Om Next needs to be bumped to alpha47 to work with 1.9.293
I'd first check if that works
wrt untangled-websocket, how do I get a tree of data that is pushed to the client to be automatically normalized? It doesn’t go through the usual untangled load-data that accepts a query. In the cookbook example, the pushed data is manually inserted into app state via functions. Do I have to dig into om.next’s merge and db<->tree?
@anmonteiro Thanks. As long as I know it should work I'll keep messing with it. I have tried explicitly requiring [org.omcljs/om "1.0.0-alpha47"] to override untangled's default there. I also tried bumping several other libraries. If you have it working without issue with ClojureScript 1.9.293, then it's something in my setup somewhere, will just have to find it.
@currentoor Yes, but low priority
@ianchow look at merge-state! in core. It allows you to supply a query for normalization, and was made just for that purpose. Has nice ident integration stuff too
hello, I'm trying to update here as well and I can't compile with Untangled anymore, using cljs 1.9.293
, om alpha-47
and untangled-client 0.5.7
hey sorry
so what’s up @wilkerlucio
oh, latest cljs not working?
what’s new in it?
@tony.kay I'm not sure the issue yet, I just got back on my computer now, I did some discussion with @anmonteiro at #om channel about it, maybe something related to transit, not sure yet
I see. So probably an Om thing, not Untangled
@wilkerlucio I’m running om-47 and untangled client 0.5.7 and not having any problems, but we’re on cljs 1.8
the problem seems related to the new version of ClojureScript, the 1.9.293
reverting to 1.9.229
works fine