I am following this thread with great interest, as I intend to do pretty much the same thing that Dave Della Costa describes, questions/clarifications in-line below:
On Apr 3, 2014, at 5:48 AM, David Nolen <[email protected]> wrote: > On Thu, Apr 3, 2014 at 8:21 AM, Dave Della Costa <[email protected]> > wrote: > (def our-data (atom {:some {:path [{:id 1} {:id 2}]}})) > > (root root-component our-data ...) > > If I have a nested component that maps to :path, and then I receive an > update from outside of Om--path may have been a cursor initially, but > after I call > > ;; totally outside of Om: > (swap! our-data #(update-in % [:some :path] ...)) > > then path is no longer a cursor. > > Not possible, if it is, this is a bug. Need a minimal example of a case where > you think this happens. Make sure that you are not accidentally putting seqs > into your application state. My understanding based on David Nolen's response to the above is that the swap! into the application state atom from outside of Om is OK, is that correct? Then David Nolen goes on to state: > It's not so much that you approach will not be supported, rather you are > opting yourself out of current benefits (:tx-listen state chage deltas for > example) and in the future likely rendering optimizations. Which I take to mean that when you change application state outside of Om as described above, then you will not obtain the benefit of some current/upcoming Om features, again, is this the correct interpretation? If so, is there any potential way that might enable "outside of Om application state changes" to make themselves compatible with (or become) "inside of Om app state changes"? For example, might it be possible to provide an input queue/channel (to Om) of app-state change requests that could be transact!/update! -ed at some point in the Om lifecycle/flow? -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
