Controller Actions opinion

Option1.js

/*  
  Option 1 is the emberist way of doing it.   
  But I find that it makes it harder to group code in larger controllers.
*/
BC.Controller.AssetDialog = BC.Controller.extend({
  actions: {
    showReference: function(reference) {
      /* Open reference dialog */
    }
  }
});

// NOTE: MY PLAN IS TO DO THIS ^^ FOR OUR WIDGETS SINCE THEY'RE SMALLER AND OFTEN ONLY HAVE ONE ACTION, IF THAT. //

Option2.js

/*  
  Option 2 is a more verbose, you can see what arguments are expect for the action.  
  But overall feels like you end up looking at pointless code.
*/
BC.Controller.AssetDialog = BC.Controller.extend({
  showReference: function(reference) {
    /* Open reference dialog */
  },
  actions: {
    showReference: function(reference) {
      this.showReference(reference);
    }
  }
});

Option3.js

/*
  Option 3 makes it more concise, but feels just like a complete by-pass of Ember.
*/
BC.Controller.AssetDialog = BC.Controller.extend({
  showReference: function(reference) {
    /* Open reference dialog */
  },
  actions: {
    showReference: BC.actionAlias('showReference')
  }
});

// Global Helper
BC.actionAlias = function(name) {
  return function() { 
    this[name].apply(this, arguments);
  };
};

Discourse seems to take Option1 in some cases and Option2 in others: https://github.com/discourse/discourse/blob/master/app/assets/javascripts/discourse/controllers/composer_controller.js#L23-L49