On Monday, March 17, 2014 11:51:32 AM UTC-7, Scott Nelson wrote: > Thanks David! That works great. I made a root component that simply builds a > new component based on the current route (updated the Gist).
One thing I might suggest is to avoid mutating app-state in your route actions. Our team has found this can lead to code that becomes difficult to reason about and test, especially when you start involving actions that need to hit the network. To get around this we either a) return a map of the next-state from the action and pass that to reset! in the navigate listener or b) use pub/sub with topic strictly for updating app-state outside of components. -- 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.
