Agreed, but it's the one thing that makes this backward compatible with
controller, which is a big win.

On Thursday, May 15, 2014, James Smith <notifications@github.com> wrote:

> In src/marionette.object.js:
>
> > +  this.options = options || {};
> > +
> > +  if (_.isFunction(this.initialize)) {
> > +    this.initialize(this.options);
> > +  }
> > +};
> > +
> > +Marionette.Object.extend = Marionette.extend;
> > +
> > +// Object Methods
> > +// --------------
> > +
> > +_.extend(Marionette.Object.prototype, {
> > +  destroy: function() {
> > +    var args = Array.prototype.slice.call(arguments);
> > +    this.triggerMethod.apply(this, ['destroy'].concat(args));
>
> I never understood why we passed the args along to this
> triggerMethod...have any of you ever used this? I feel like it's a bad way
> to communicate information from an object A triggering destroy on this obj
> to an object B listening in on the object. Could we get rid of this?
>
> this.triggerMethod('destroy');
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/marionettejs/backbone.marionette/pull/1323/files#r12720077>
> .
>


-- 

-- 
Jason Laster
*Software Engineer*
  Etsy