Update vnodes.md
This commit is contained in:
parent
1b0899b469
commit
3a633ce99c
1 changed files with 2 additions and 2 deletions
|
|
@ -116,7 +116,7 @@ When creating libraries that emit vnodes, you should use this module instead of
|
||||||
|
|
||||||
Vnodes are supposed to represent the state of the DOM at a certain point in time. Mithril.js's rendering engine assumes a reused vnode is unchanged, so modifying a vnode that was used in a previous render will result in undefined behavior.
|
Vnodes are supposed to represent the state of the DOM at a certain point in time. Mithril.js's rendering engine assumes a reused vnode is unchanged, so modifying a vnode that was used in a previous render will result in undefined behavior.
|
||||||
|
|
||||||
It is possible to reuse vnodes in place to prevent a diff, but it's preferable to use the [`onbeforeupdate`](lifecycle.md#onbeforeupdate).
|
It is possible to reuse vnodes in place to prevent a diff, but it's preferable to use the [`onbeforeupdate`](lifecycle-methods.md#onbeforeupdate).
|
||||||
|
|
||||||
#### Avoid passing model data directly to components via attributes
|
#### Avoid passing model data directly to components via attributes
|
||||||
|
|
||||||
|
|
@ -174,4 +174,4 @@ var BetterListComponent = {
|
||||||
}))
|
}))
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue