abstract-state-router - npm Package Versions

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.