Ember Controller vs Ember ArrayController

Question

关于何时使用Ember.Controller以及何时使用Ember.ArrayController及其用法，我没有明显区别。

Answer 1

With a Controller, you could do {{#each item in model}} in your template.

With ArrayController, you could simply do {{#each item}} .

Could. ArrayController is deprecated because it was obscuring the logic, you should never use it. The Controller is also being deprecated in favor of routeable components, somewhere in Ember 2.1 or 2.2.

Current strategy is the following:

• Forget ArrayController, ObjectController and View.
• Use components for everything.
• Until Ember 2.1/2.2, you're unable to use a component for a root template of any route. For that template, you'll have to use a controller.
• Don't put any logic into that controller. Simply place a component in its template and pass the model through. Use such controllers only for query params and other stuff that components are incapable of (yet).
• In routes, don't use setupController . Instead, put everything into a model, turning it into a hash of models. RSVP.hash is your friend.
• When routable components are available, replace controllers with components.

PS The syntax for each is changing to {{#each model as |item|}} .