-
Notifications
You must be signed in to change notification settings - Fork 9
Ui router vs angular routing
Jens Melgaard edited this page Oct 18, 2013
·
3 revisions
Some of these are probably more subjevtive that objective, but I will try to be as fair to UI Router as I can.
- Seperation of Application State and View State
- Full support for transition control between state, not just enter/exit or a global state changed handler
- A Simpler view model that still adds more flexibility through the view service
- Sibling lookup in terms of "next" and "prev".
- Parameter converters, UI Router has support for regex parameters but it seems more limited
- Providing means to simply refresh views rather than reloading templates as well (see sticky and $view-refresh)
- No un-nanmed views.
- No abstract states. (Angular Routing don't need them)
- No support for route matching through functions.
- Less used.
- Bigger footprint.
- Not compatible with angular 1.0.x
- Route Provider
- Basic Configuration
- Parameters and Converters
- Decorators
- Case Sensitivity
- A Word on Trailing Slashes
- Legacy Support
- State Provider
- Basic Configuration
- Hierarchy Configuration
- Views
- Routes
- Transitions
- Resolve
- State Service
- Transition Provider
- Basic Configuration
- Stage Handlers
- Targeting Multiple States
- View Provider
- Updating Views
- Transactions
- Scroll Provider