... | @@ -34,7 +34,7 @@ |
... | @@ -34,7 +34,7 @@ |
|
|
|
|
|
#### Unidirectional architecture implementation
|
|
#### Unidirectional architecture implementation
|
|
|
|
|
|
Each application module will have its **own store/state instance** (singleton pattern). The file module is called `State.js`. So the application state is the addition of the modules states. The application itself also has its own state instance that holds application scope state, e.g. the current `code` selected. In this case the various modules can subscribe to the `code` change event.
|
|
Each application module will have its **own store/state instance** (singleton pattern). The file module is called `State.js`. So the application state is the addition of the modules states. The application itself also has its own state that holds the application scope state, e.g. the current `code` selected. In this case the various modules can subscribe to the `code` change event.
|
|
|
|
|
|
As the state instance is local to the application module we will try to have an implementation as simple and specific as possible (more semantic and less general, flexible and complex). Even this can be a bit different among different app modules.
|
|
As the state instance is local to the application module we will try to have an implementation as simple and specific as possible (more semantic and less general, flexible and complex). Even this can be a bit different among different app modules.
|
|
|
|
|
... | | ... | |