trek / ember-evented-checkbox Goto Github PK

This is really a problem with Ember, which trickles into this project. Ember.Evented creates it's own concept of an "event", unrelated to window.Event, which itself is confusion right off the bat. On top of this, actions aren't related to Ember.Evented in any way, except that you may use one to trigger the other. This again, is confusing.

How this related to this project is that it's unclear what an "evented-checkbox" is. It uses Ember.Evented internally, but this is more of an implementation detail rather than the merit, which seems to me that it emits an Ember action on change. While we can't solve Ember's naming conventions here, I wonder if this project and components could be named more accurately; something like <actionable-checkbox> or something.

This may seem like bikeshedding (OK...maybe it is)..but this project is an important testing ground for future Ember IMO and the sooner we start reconciling action vs. ember event vs. window.Event the better.