abstract-state-router - npm Package Compare versions

Comparing version 5.16.0 to 5.16.1

changelog.md

		@@ -0,1 +1,8 @@
		# [5.16.1](https://github.com/TehShrike/abstract-state-router/releases/tag/v5.16.1)


		- documentation: fixed a requre/require typo [#103](https://github.com/TehShrike/abstract-state-router/pull/103)
		- documentation: added "inherit" to the documented `go()` options [#104](https://github.com/TehShrike/abstract-state-router/pull/104)
		- documentation: in the rendered docs, fixed the link to the ractive example source code [8511b651](https://github.com/TehShrike/abstract-state-router/commit/8511b651de025af466e70cc9fb0bfa5c3ad351f6)

		# [5.16.0](https://github.com/TehShrike/abstract-state-router/releases/tag/v5.16.0)
		@@ -8,3 +15,3 @@
		- updated hash-brown-router [#93](https://github.com/TehShrike/abstract-state-router/pull/93)
		- compatibility: switched from `requre('events').EventEmitter` to `requre('events')` for better Rollup compatibility. [c861f5ab](https://github.com/TehShrike/abstract-state-router/commit/c861f5ab2d0c5d34915c6344fc8ef2d5a7982db2)
		- compatibility: switched from `require('events').EventEmitter` to `require('events')` for better Rollup compatibility. [c861f5ab](https://github.com/TehShrike/abstract-state-router/commit/c861f5ab2d0c5d34915c6344fc8ef2d5a7982db2)

		@@ -11,0 +18,0 @@ # [5.15.0](https://github.com/TehShrike/abstract-state-router/releases/tag/v5.15.0)

package.json

		{
		"name": "abstract-state-router",
		"version": "5.16.0",
		"version": "5.16.1",
		"description": "Like ui-router, but without all the Angular. The best way to structure a single-page webapp.",
		@@ -5,0 +5,0 @@ "main": "index.js",

readme.md

		@@ -174,3 +174,5 @@ abstract-state-router lets you build single-page webapps using nested routes/states. Your code doesn't reference routes directly, like `/app/users/josh`, but by name and properties, like `app.user` + `{ name: 'josh' }`.

		The options object currently supports just one option "replace" - if it is truthy, the current state is replaced in the url history.
		The options object currently supports two options:
		- `replace` - if it is truthy, the current state is replaced in the url history.
		- `inherit` - if true, querystring parameters are inherited from the current state. Defaults to false.

		@@ -177,0 +179,0 @@ If a state change is triggered during a state transition, and the DOM hasn't been manipulated yet, then the current state change is discarded, and the new one replaces it. Otherwise, it is queued and applied once the current state change is done.

renderer.md

		@@ -124,3 +124,3 @@ # Create your own renderer

		You'll need to implement those in order to get the example todo app working. See the Ractive `app` state template [here](https://github.com/TehShrike/state-router-example/blob/gh-pages/implementations/ractive/app/app.html#L5-L7) using the Ractive decorator exposed by ractive-state-router that sets an `active` class on the element when the given state name is active, and the `makePath` function that builds a url to a state given a state name and some properties.
		You'll need to implement those in order to get the example todo app working. See the Ractive `app` state template [here](https://github.com/TehShrike/state-router-example/blob/master/implementations/ractive/app/app.html#L5-L7) using the Ractive decorator exposed by ractive-state-router that sets an `active` class on the element when the given state name is active, and the `makePath` function that builds a url to a state given a state name and some properties.

		@@ -127,0 +127,0 @@ You can implement these with functionality exposed by the state router:

New alerts