1

I have read these answers by Izhaki and Artem Platonov on Understanding Design Patterns and have some questions about this approach. They might be trivial, but I need some answers.

The final answer by Itzhaki made it seem to me that Angularjs design pattern is kinda MVW (MODEL VIEW WHATEVER), but I think I still haven't got 'Model' fully.

View(DOM) -> Controller -> Service(Application login) -> Model(like resource)

If this pattern goes in this way, Where is Located all the information about the whole system?

For example: Assuming that we have some properties about a "game" such as number of players, number of groups, etc.

Where is all of this data being encapsulated?

With es6 JS, I was thinking about making a class called Game with its own properties;

Where do I need to locate this class?

Community
  • 1
  • 1
Elad Israeli
  • 131
  • 2
  • 11
  • Possible duplicate of [Why is AngularJS considered MV\*](http://stackoverflow.com/questions/26165408/why-is-angularjs-considered-mv) – Paul Sweatte Jul 11 '16 at 16:12
  • Possible duplicate of [DIsplay angular 2 decorator metadata in the browser](http://stackoverflow.com/questions/40626165/display-angular-2-decorator-metadata-in-the-browser) – Paul Sweatte Jan 19 '17 at 06:02

0 Answers0