Hi Todd, > So, for example, if you edit all 3 fields, it causes 3 saves to be > sent, which isn't what I want at all.
Can you go into a bit more detail about why this is the case? I can say that whatever the case may be, I would be hesitant to incorporate any logic for how the server should receive updates anywhere but in the tx-listen function. DD (2014/07/10 14:48), Todd Berman wrote: > I am working on an editor component that allows editing for (for > example) 3 fields (using an editable subcomponent) on a single > object. When the object is saved, the individual editors are told to > save using a channel, which causes a problem on my :tx-listen > callback, since it is saving data back to the server. > > So, for example, if you edit all 3 fields, it causes 3 saves to be > sent, which isn't what I want at all. > > One option that I would like to try is to have the editor component > gather key paths and new values from its editable subcomponents, and > then save it in a single batch. However, I can't see how to batch > multiple edits into a single 'transaction'. > > It seems that my best option is to gather the key paths and new > values, and then save them and add a :tag to the last one that > triggers the :tx-listen callback to actually save the data back to > the server. > > Am I missing something obvious that would make this simpler? > > --Todd > -- 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.
