This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-03-30
Channels
- # admin-announcements (10)
- # beginners (17)
- # boot (14)
- # braveandtrue (4)
- # cider (6)
- # cljsrn (38)
- # clojure (232)
- # clojure-austin (1)
- # clojure-belgium (2)
- # clojure-dev (20)
- # clojure-greece (20)
- # clojure-japan (3)
- # clojure-poland (39)
- # clojure-russia (76)
- # clojure-sanfrancisco (6)
- # clojure-uk (4)
- # clojurescript (90)
- # cursive (2)
- # data-science (10)
- # datomic (18)
- # garden (16)
- # hoplon (244)
- # immutant (3)
- # jobs (6)
- # jobs-discuss (2)
- # juxt (1)
- # off-topic (3)
- # om (50)
- # onyx (23)
- # re-frame (5)
- # reagent (36)
- # remote-jobs (11)
- # slack-help (6)
- # spacemacs (2)
- # untangled (46)
What are you not able to do on the server side? I don't understand the 'up in the air' comment.
react-motion will call your child-fn from RAF, so need to manually convey bindings for the factories in child-fn. after that, so far so good..
hi, is there an official api to get the state history in om.next (alpha33-SNAPSHOT)?
I'm showing om.next at a local react.js meetup, I already have the export/import state like circleci
but I would like to enable a time traveling widget with the last N values of the state atom
@marianoguerra: I've never used it yet but it looks like om.next/from-history
will do what you need
@seanirby: thing is I need to get the uuid from somewhere
if can I subscribe to the thing that logs in the console to collect the uuids then I'm done
the alternative is to call app-staet and add-watch
@marianoguerra: no public API
maybe you can dig around https://github.com/omcljs/om/blob/master/src/main/om/next/cache.cljs
and find something that solves your problem
I think I will call add-watch on the atom returned from app-state and see if it works
I think the nice official way would be to be able to subscribe to the transactions and move the logging as a subscriber of that API
hey @anmonteiro, i noticed when bumping my version from alpha30 to alpha32 that :normalize true
had no effect when I passed an atom to the reconciler. do you know if this is a regression or is the reconciler expecting a map for normalization to occur?
add-watch works like a charm
@seanirby: the only thing that jumps to mind is this commit: https://github.com/omcljs/om/commit/6243eb499b865894ba680cb8e6c56db9d404d8a8
I'll try it out later and let you know if there's a regression
@dnolen: there's no symbol-identical?
in Clojure
My fix was to pass a map, then (defonce app-state (om/app-state app-reconciler))
to get ahold of the atom
tomjack: I haven't needed to pull the app-state out of the reconciler yet. I've just been using @reconciler. What's the difference?
@dnolen: just noticed we have dispatch
repeated in 3 places: om.next.impl.parser
, om.next
and om.next.server
I think just punted because it’s not very important and I didn’t want to think about where to put it
not sure if it's too much of a problem, since it's a very simple thing
yea.. we could probably do (def dispatch om.next.impl.parser/dispatch)
on the others if we want to avoid the repetition
since parser can be imported in both clj and cljs
because of advanced optimizations?
exactly
alright, just something I noticed, not much we can do about it then