Could not fire callback on update about rubberduck

[Thomas-P]

I think it could be a problem, if you use not the param-parameter. Would it be possible to make them optional?

[daffl]

The params parameter can be optional if you take care of it in your service:

find: function(params, callback) {
  if(!callback) {
    callback = params;
    params = {};
  }
}

Standard services do require params however. Do you have an example for the error?

[Thomas-P]

Thats ok, but i get trouble by sending from client something like this:

socket.emit('todo::create', {
  description: 'I really have to iron'
}, function(error, data) {
}); // params aren't setted.

Then i got also a function, but they called ack and throws an error.

[daffl]

That probably won't work in the latest version without sending an empty parameters object like

socket.emit('todo::create', {
  description: 'I really have to iron'
}, {}, function(error, data) {
}); // params aren't setted.

I created an issue because it will probably be fairly easy to make this possible.

[Thomas-P]

Thats nice, thanks.