mithril - npm Package Compare versions

docs/vnodes.md

		@@ -115,7 +115,7 @@ <!--meta-description

		#### Avoid memoizing mutable vnodes
		#### Avoid reusing vnodes

		Vnodes are supposed to represent the state of the DOM at a certain point in time. Mithril.js' 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 to prevent a diff, but it's preferable to use the `onbeforeupdate` hook to make your intent clear to other developers (or your future self).
		It is possible to reuse vnodes in place to prevent a diff, but it's preferable to use the [`onbeforeupdate`](lifecycle.md#onbeforeupdate).

		@@ -122,0 +122,0 @@ #### Avoid passing model data directly to components via attributes

package.json

		{
		"name": "mithril",
		"version": "3.0.0-next.23",
		"version": "3.0.0-next.24",
		"description": "A framework for building brilliant applications",
		@@ -5,0 +5,0 @@ "author": "Leo Horie",

New alerts