I like the thinking. I would prefer collection be the property name on ArrayController.

And to use Ember.alias to implement.

@lukemelia I'll be pushing a change in a moment with this and tests

I'm not sure what is special about the content property but Ember is not allowing me to alias it. I can alias computed properties, other functions, and string literals without issue but when I alias content I get null. Any thoughts? /cc @wycats

The concern I have about this is that in the Route, you use the model hook for both. It seems weird to use the model hook in the route but a models hook in the controller.

Also, I think of the Array as the "model" for the template, even though the model happens to be an Array.

Thoughts?

Why not auto-set the controller's model property if the Router has a model assigned? This would clean up ome coe and is a pattern that everybody is doing already

Also, I feel that either models or collection will be preferred over the singular model for the ArrayController. I like @lukemelia's collection suggestion. But, I can see where the vocabulary is getting too "backbone-y"

I think it should model, if you want collection, then singular should be record or resource. model is kind of generic.

I slept on it, I agree with @wycats and @tchak that model is ideal for both situations.

I came to the same conclusion. :)