Question on having quickform call a meteor method and then routing to another route

Using a quickform like this:

  {{> quickForm collection="Books" id="updateBookForm" doc=this type="method-update" meteormethod="updateBook"}}

Which then calls the updateBook method when submitted:
(This code is shared on client and server)

  insertBook: function (theBook) {
    console.log('inserting book ', theBook);
  updateBook: function (modifier, id) {
    console.log("updateBook method running updating these fields", modifier);
    console.log("for this document id:", id);
    Books.update(id, modifier);

But when updateBook is called by autoform, I get this exception on the server:

I20150427-09:40:37.530(-5)? Exception while invoking method ‘updateBook’ TypeError: Object function router(req, res, next) { // 13
I20150427-09:40:37.531(-5)? //XXX this assumes no other routers on the parent stack which we should probably fix // 14
I20150427-09:40:37.531(-5)? router.dispatch(req.url, { // 15
I20150427-09:40:37.531(-5)? request: req, // 16
I20150427-09:40:37.531(-5)? response: res // 17
I20150427-09:40:37.531(-5)? }, next); // 18
I20150427-09:40:37.531(-5)? } has no method 'go’
I20150427-09:40:37.531(-5)? at [object Object].Meteor.methods.updateBook (app/quickformdemo.js:38:14)

I have discovered that wrapping the Router.go call with Meteor.lsClient solves the issue, but I’m just wondering if I’m missing something… is this the only / best way to do this?

So did u find the answer?

In this case keeping the routing call client side only is the way to go. Using a Meteor.isClient check around the Router.go('/') call in the method will do this, as will a isSimulation check. A better option however might be to remove the routing call from the method completely, to reduce clutter in the method, since it’s likely better handled in another location (like in a template event).