om/update! is working on the cursor's view/entry-point into the app state atom, not directly with the entire atom you've declared to hold your app state.
On Jul 16, 2014, at 8:31 PM, Andrew Stoeckley <[email protected]> wrote: > On Saturday, January 25, 2014 11:38:14 PM UTC+8, David Nolen wrote: >> >> If I was to describe the difference between Om and Reagent it would be that >> Om is draconian about component modularity in order to encourage component >> reuse. Directly manipulating the app state from a component in Om is a >> anti-pattern. > > Can I get a bit of clarification on this: The above suggests an anti-pattern > but isn't the idea that app state be manipulated using om/update! or > om/transact! both of which must be called inside a component function? > > Or are you suggesting that it is the passing of the entire app-state to a > component rather than a specific cursor that is the anti-pattern? > > -- > 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. -- 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.
