vndb/mithril-vndb
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

lint links

Browse source
This commit is contained in:
Leo Horie 2017-01-08 21:29:26 -05:00
parent e4d69c409a
commit d397e66e03
5 changed files with 26 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/render.md
View file

@ -54,7 +54,7 @@ In contrast, traversing a javascript data structure has a much more predictable
### Differences from other API methods
`m.render()` method is internally called by [`m.mount()`](mount.md), [`m.route()`](route.md), [`m.redraw()`](redraw.md) and [`m.request()`](request.md). It is not called by [`m.prop()`](prop.md)
`m.render()` method is internally called by [`m.mount()`](mount.md), [`m.route()`](route.md), [`m.redraw()`](redraw.md) and [`m.request()`](request.md). It is not called after [stream updates](stream.md)
Unlike with `m.mount()` and `m.route()`, a vnode tree rendered via `m.render()` does not auto-redraw in response to view events, `m.redraw()` calls or `m.request()` calls. It is a low level mechanism suitable for library authors who wish to manually control rendering instead of relying on Mithril's built-in auto-redrawing system.