Hi Slaven, This is mostly a matter of preference. I don't like to use classes for my model's but just the pure data. If I need special handling in my records for validation, or calculation or whatever, I usually create a companion class, that hold all this functionality, and accepts a 'record' as it's parameters. I need to instantiate just 1 of those, and not as many as I have records. This might be a huge save. However, If you have a table that's just 1 or very few rows, you might want to use a class, as this is in some cases a little easier to use.
Regards Sander -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
