Okay—that was my assumption as well, it just seemed like that wasn’t what was happening.
I’m still not clear on where a server-side mutation’s value is stored in the client-side state—when I look at my state atom I don’t seem to see that value associated with a key. > On Jun 8, 2016, at 11:08, David Nolen <[email protected]> wrote: > > That's what server-side mutations do there's nothing to wait for. If you're > talking about some kind of push state thing, there's nothing stopping you > from implementing that today and people already have. > > David > > On Wed, Jun 8, 2016 at 11:11 AM, Max Countryman <[email protected] > <mailto:[email protected]>> wrote: > Hi David, > > Thanks for letting me know! > > In the future, should I expect a server-side mutation function to have the > capability of updating client-side state? > > > Max > > -- > 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] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/clojurescript > <https://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 https://groups.google.com/group/clojurescript.
