Prefer hash for event payloads? about javascript HOT 2 CLOSED

👍 I agree with this convention for the reasons above, plus:

• jQuery only allows you to pass one data argument to trigger (other systems lack this limitation)
• it is more straightforward to re-raise an event when you only have one data argument, versus having to slice or apply arguments in order to coordinate with a multi-argument calling convention

On that subject, I believe you have a bug in your example code. The callbacks passed to jQuery.fn.on will receive a jQuery.Event instance as the first argument, followed by the data passed to trigger.

I do have the following hesitations, which I hope somebody else will second or assuage:

• Backbone.Events bucks this convention; when subscribing to the all event, the first argument will be the event name followed by the remaining trigger payload
• Furthermore, a significant number of Backbone.Events will pass an instance to the object that triggered the event as the first (and often only) argument

from javascript.

@jamesreggio Ah, good catch. Updated my examples. However, I'm not sure how your hesitations apply—it seems like whenever you're passing a data payload with an event, you can pass an object instead of a value, regardless of the system involved.

from javascript.