@untool/core - npm Package Compare versions

Comparing version 1.0.0-rc.8 to 1.0.0-rc.9

CHANGELOG.md

		@@ -6,2 +6,10 @@ # Change Log

		# [1.0.0-rc.9](https://github.com/untool/untool/compare/v1.0.0-rc.8...v1.0.0-rc.9) (2018-11-15)

		Note: Version bump only for package @untool/core





		# [1.0.0-rc.8](https://github.com/untool/untool/compare/v1.0.0-rc.7...v1.0.0-rc.8) (2018-10-23)
		@@ -8,0 +16,0 @@

package.json

README.md

		@@ -166,4 +166,6 @@ # `@untool/core`

		If inheriting from `Mixin`, all methods of your mixin are automatically bound to the repective instance, so you do not have to call `this.method.bind(this)` yourself even if you use them in asynchronous contexts.
		If inheriting from `Mixin`, all mixinable methods of your mixin are automatically bound to the respective instance, so you do not have to call `method.bind()` yourself even if you use them in asynchronous contexts.

		While it is technically possible to define non-mixin utility methods on your mixin, doing so is strongly discouraged. If you have to, however, it is recommended to prefix such methods' names with an underscore (`_`) to denote them as private.

		Note that you can call all defined mixinable methods directly on your mixin instance.
		@@ -170,0 +172,0 @@

New alerts