examples/server -> examples/server-rendering

This commit is contained in:
Yoshua Wuyts
2016-05-23 14:45:24 +09:00
parent dc840059a4
commit ab96d51a89
5 changed files with 4 additions and 3 deletions
+4 -3
View File
@@ -125,13 +125,14 @@ document.body.appendChild(tree)
`models` are objects that contain initial `state`, `subscriptions`, `effects` `models` are objects that contain initial `state`, `subscriptions`, `effects`
and `reducers`. They're generally grouped around a theme (or domain, if you and `reducers`. They're generally grouped around a theme (or domain, if you
like). To provide some sturdiness to your `models`, they can either be like). To provide some sturdiness to your `models`, they can either be
namespaced or not. Namespacing means that only actions and state inside the namespaced or not. Namespacing means that only state within the model can be
model can be called. accessed. Models can still trigger actions on other models, though it's
recommeded to keep that to a minimum.
So say we have a `todos` namespace, an `add` reducer and a `todos` model. So say we have a `todos` namespace, an `add` reducer and a `todos` model.
Outside the model they're called by `send('todos:add')` and Outside the model they're called by `send('todos:add')` and
`state.todos.todos`. Inside the namespaced model they're called by `state.todos.todos`. Inside the namespaced model they're called by
`send('add')` and `state.todos`. An example namespaced model: `send('todos:add')` and `state.todos`. An example namespaced model:
```js ```js
const app = choo() const app = choo()
app.model({ app.model({