I'm having a tough time figuring out the best path for modeling server data. Up to now, I've had luck using classes that contain related data and functionality and a manager for each of these classes that monitors the pool of classes I've downloaded from the server. The problem I'm running into is within more complicated views that need access to nested relationships of these objects. Like Object A has an id reference to 3 other classes - so now I've got to go hit three other managers to find the related properties for Object A. I'm basically left doing per-view object compositions.
I'm trying to formulate some possibilities that seem like they will scale in the future, and I keep coming back to the idea of ditching these class models entirely and handling the server data on a per-view basis - i.e. no consistent model. Can any of you offer design suggestions, pros and cons or examples? Thanks, Jonathan -- You received this message because you are subscribed to the Google Groups "AngularJS" 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.
