angularjs数据组织服务与范围

Question

100 different , with all there own origin (country), preparation time, difficulty etcetera).

the two (next to each other);

1. filter (by country, preparation time, difficulty ...)
2. List (meals which meet the filter criteria)

-What are the advantages of putting all the meals in a meal with respect to putting them directly on the scope?

• should I have an object inside the mealservice which holds the filters (eg filters={'country':'germamy', 'maxPrepTime':50}

• should I have an object inside the mealservice which holds the selected meals, if for example an country is added to the searchcriterea this list is directly updated (in the view only ng-repeat will be required for this list)

• should I define my own filter ( ng-repeat="meal in meals" | customFilter " )

• other method?

Thanks in advance!!!

Answer 1

As a best practice you should always have fat models and thin controllers .

One of the most important arguments to make so is, that it will be much easier to reuse your code if it's encapsulated in a service/factory then if it's implemented in the controller.

You can also implement you own filter, but it can actually use a method from the service.