Skip to content

Latest commit

 

History

History
179 lines (98 loc) · 12.3 KB

changelog.md

File metadata and controls

179 lines (98 loc) · 12.3 KB
Raw

7.6.0

  • feature: the canLeaveState function now gets passed a second argument with the name+parameters of the state that the user is trying to navigate to
  • technically a breaking change: the previously undocumented stateChangePrevented function now gets passed a name+parameters object as its first argument, instead of just the name of the current state. Also, it gets passed a second argument with the name+parameters of the state that the user attempted to visit.

7.5.2

Fix: only call canLeaveState on states that are going to be destroyed, not the ones that are going to get created.

7.5.1

Fix a bug that could cause canLeaveState to be called twice. #155

7.5.0

Add canLeaveState to addState, so you can implement route guards to prevent people from navigating away from a state if they e.g. have unsaved state. #154

7.4.0

Support passing in a null state name to stateIsActive.

7.3.1

Fixes an issue where when a state was destroyed and resolved during the same state change, the result of its resolve function would get tossed out.

7.3.0

Removes the concept of resetting states.

The concept of resetting breaks down if your component library doesn't support

  • slots
  • resetting the state of a component without resetting the contents of slots

For renderers that "reset" states by destroying the existing component and re-constructing it, stuff would break in any case where a parent and child state were both told to reset at once. Whenever the parent would reset and destroy its part of the DOM, the child would get wiped out.

Existing renderers don't need to change to work with this version of ASR, it's just that their reset function won't get called any more.

The beforeResetState and afterResetState should not be fired any more.

7.2.0

  • Coerce parameter values to strings for comparison in stateIsActive #151

7.1.0

  • Give an explicit/useful error message if you forget to add a ui-view element to a parent template #148

7.0.0

  • maintenance: update a bunch of dependencies #141
  • maintenance: autoformat the scripts to make myself feel better and reduce commit noise in the future #145
  • breaking: dropped ES5 support. If you're targeting ES5 you'll need to compile it in your own app's build.

6.2.0

  • feature: allow dynamic parameter defaults via functions #144

6.1.0

  • feature: added getActiveState method #121

6.0.5

  • maintenance: added a bunch of files to the .npmignore to reduce the package download size

6.0.4

  • bug fix: update the hash-brown-router dependency to fix an issue where calling evaluateCurrent('somestate') wouldn't do anything when somestate's route was / and the current url was also /. Issue #116 in abstract-state-router, commit #56c207f0 in hash-brown-router. If you're passing in your own hash-brown-router instance, make sure to update it to 3.3.1 to avoid the bug.

6.0.3

  • bug fix: point package.main at the ES5 bundle instead of the ES2015 code :-x 34ea0baa

6.0.2

  • bug fix: fixed a crash that would happen if you didn't pass an options object in 3b60669b

6.0.1

  • dependency update: changed hash-brown-router dependency from ~3.2.0 to ^3.3.0 a593408b

6.0.0

  • Promise and Object.assign polyfills are now required for older browsers
  • refactor: updated all the source code to ES2015 (though the published version is still compiled down to ES5)

5.17.0

  • functional: stateChangeStart and stateChangeEnd events now also emit the full array of states being transitioned to. #113

5.16.3

  • documentation: added a table of contents to the API section of the readme #111

5.16.2

  • drop dependencies on the process and events polyfills and bump hash-brown-router dependency, saving about 25KB

5.16.1

  • documentation: fixed a requre/require typo #103
  • documentation: added "inherit" to the documented go() options #104
  • documentation: in the rendered docs, fixed the link to the ractive example source code 8511b651

5.16.0

  • updated hash-brown-router to 3.1.0, making the / route equivalent to an empty route string #102

5.15.1

  • updated hash-brown-router #93
  • compatibility: switched from require('events').EventEmitter to require('events') for better Rollup compatibility. c861f5ab

5.15.0

  • functional: renderers may now return a new DOM API from the reset function. c07a45fb

5.14.1

  • bug fix: empty strings in default parameters would cause the state router to stop cold without any error message #2abf9361

5.14.0

  • functional: replaced the defaultQuerystringParameters property on states with defaultParameters, which applies to both querystring and route parameters. If you don't specify defaultParameters, defaultQuerystringParameters will be checked too (though it will now apply to route parameters as well). #91

5.13.0

  • functional: made stateName optional for go/replace/makePath #83

5.12.5

  • dependency update: require page-path-builder 1.0.3, fixing a path-building bug #650af6af

5.12.4

  • bug fix: stateIsActive was doing an extremely naive check #71

5.12.3

  • bug fix: makePath(stateName, params, { inherit: true }) now properly inherits route parameters during the render/activate phases #7617d74b

5.12.2

  • bug fix: fixed Webpack build by changing a JSON file to CommonJS #65

5.12.1

  • bug fix: states that had child states without routes weren't necessarily loading the correct child state when you browsed to them #85112c79

5.12.0

5.11.0

5.10.0

5.9.0

  • functional: added emitting events before and after calling every dom rendering function #54

5.8.1

5.8.0

  • functional: changed parameters objects passed to the DOM rendering functions to be mutable copies instead of being frozen