How much logic should be in a model?


#1

I’m designing an application that performs a calculation on a bunch of user data (think tax form). At first glance, it seems Ember’s computed properties would be perfect for handling the job. But I’m reluctant to build all that business logic into the model layer. What is the right way to do this? Would I build something in to the controller? What form would that take, since I’m trying to bind the resultant values to a view and want a single source of truth?

Look forward to hearing your suggestions & thoughts.


#2

This was discussed not to long ago, I think the consensus was; computed properties are ok if all the data needed is within that model or related models. That way you don’t have to re-define the same computed property on multiple controllers.