gotchajavascriptangularCritical
What is the difference between angular-route and angular-ui-router?
Viewed 0 times
angularandbetweenroutethedifferencerouterwhat
Problem
I'm planning to use AngularJS in my big applications. I'm in the process to find out the right modules to use.
What is the difference between
In many articles when
Which module should I use for better manageability and extensibility?
What is the difference between
ngRoute (angular-route.js) and ui-router (angular-ui-router.js) modules?In many articles when
ngRoute is used, routes are configured with $routeProvider. However, when used with ui-router, routes are configured with $stateProvider and $urlRouterProvider.Which module should I use for better manageability and extensibility?
Solution
ui-router is a 3rd-party module and is very powerful. It supports everything the normal ngRoute can do as well as many extra functions.
Here are some common reason ui-router is chosen over ngRoute:
-
ui-router allows for nested views and multiple named views. This is very useful with larger app where you may have pages that inherit from other sections.
-
ui-router allows for you to have strong-type linking between states based on state names. Change the url in one place will update every link to that state when you build your links with
-
There is also the concept of the decorator which could be used to allow your routes to be dynamically created based on the URL that is trying to be accessed. This could mean that you will not need to specify all of your routes before hand.
-
states allow you to map and access different information about different states and you can easily pass information between states via
-
You can easily determine if you are in a state or parent of a state to adjust UI element (highlighting the navigation of the current state) within your templates via
In essence, ui-router is ngRouter with more features, under the sheets it is quite different. These additional features are very useful for larger applications.
More Information:
Here are some common reason ui-router is chosen over ngRoute:
-
ui-router allows for nested views and multiple named views. This is very useful with larger app where you may have pages that inherit from other sections.
-
ui-router allows for you to have strong-type linking between states based on state names. Change the url in one place will update every link to that state when you build your links with
ui-sref. Very useful for larger projects where URLs might change.-
There is also the concept of the decorator which could be used to allow your routes to be dynamically created based on the URL that is trying to be accessed. This could mean that you will not need to specify all of your routes before hand.
-
states allow you to map and access different information about different states and you can easily pass information between states via
$stateParams.-
You can easily determine if you are in a state or parent of a state to adjust UI element (highlighting the navigation of the current state) within your templates via
$state provided by ui-router which you can expose via setting it in $rootScope on run.In essence, ui-router is ngRouter with more features, under the sheets it is quite different. These additional features are very useful for larger applications.
More Information:
- Github: https://github.com/angular-ui/ui-router
- Documentation:
- API Reference: http://angular-ui.github.io/ui-router/site/#/api
- Guide: https://github.com/angular-ui/ui-router/wiki
- FAQs: https://github.com/angular-ui/ui-router/wiki/Frequently-Asked-Questions
- Sample Application: http://angular-ui.github.io/ui-router/sample/#/
Context
Stack Overflow Q#21023763, score: 1129
Revisions (0)
No revisions yet.