Overview and Use Case
Sticky States allows two or more trees of states to run concurrently along side each other.
The initial use case for this functionality is to implement "tabs" for application modules. Using Sticky States, a single app can implement one state tree for each tab, and have them operate at the same time, in parallel to each other. Each tab is implemented as its own UI-Router state tree. While one tab is active, the other tab is inactivated, but can be reactivated without losing any work in progress.
For the tabs use case, Sticky States work best along with Deep State Redirect
Sticky State Lifecycle
A Sticky State is the root of a UI-Router state tree which can continue running even after it is "exited". The sticky state (and its children) have a different lifecycle than normal states. The views of a Sticky State (and all activated substates) are retained until one of two things happen:
- The parent of the sticky state is exited
- The parent of the sticky state is directly activated
If a sibling of the sticky state (or a child of a sibling) is activated, the sticky state tree will "inactivate". A transition back to the inactivate state will reactivate it.
Sticky states works requires
ui-router-core 2.0.0 or above.
npm ls to check the version of
ui-router-core included with the UI-Router distribution for your framework
1) Add Plugin
In Angular 1, register a plugin by injecting
$uiRouterProvider in a
In Angular 2, register a plugin in your
In React, register a plugin after creating your
;let router = ;router;
Or, if using component bootstrapping, add the plugin in your routerConfig function.
let router;return <UIRouterReact config=routerConfig/>;
2) Mark a state as sticky
The sticky state's view must have its own unique ui-view (not shared by other states). Create and target a named ui-view.
let adminModule =name: 'admin'sticky: trueviews:admin: component: AdminComponent
The AdminComponent should remain active in the
admin, even if a sibling state is activated.
3) Show/Hide the sticky component
When a sticky state is inactive, it's often desired to hide the contents from the UI.
This can be achieved using
In some cases,
ui-sref-active may also be used to toggle a class on the named
This project was ported from the UI-Router Extras project for legacy UI-Router. For more information, see the ui-router extras documentation: http://christopherthielen.github.io/ui-router-extras/#/sticky
TODO: Rewrite docs