From 74125e42c7eecf25e0e7f1ed4284b858a7421225 Mon Sep 17 00:00:00 2001 From: Scotty Simpson Date: Thu, 23 Mar 2017 08:39:49 -0700 Subject: [PATCH] m.prop() isn't a thing anymore --- docs/mount.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/mount.md b/docs/mount.md index f8a28e95..517e5cd3 100644 --- a/docs/mount.md +++ b/docs/mount.md @@ -69,7 +69,7 @@ In contrast, traversing a javascript data structure has a much more predictable ### Differences from m.render -A component rendered via `m.mount` automatically auto-redraws in response to view events, `m.redraw()` calls or `m.request()` calls. Vnodes rendered via `m.render()` do not. Note that calls to `m.prop()` do not trigger auto-redraws. +A component rendered via `m.mount` automatically auto-redraws in response to view events, `m.redraw()` calls or `m.request()` calls. Vnodes rendered via `m.render()` do not. `m.mount()` is suitable for application developers integrating Mithril widgets into existing codebases where routing is handled by another library or framework, while still enjoying Mithril's auto-redrawing facilities.