$stateProvider工作的方式与Angular's v1 router相近，但是他更加注重状态
最简单的方式可以像这样添加
当状态被激活时，他的模板会被自动插入至他父状态的ui-view中。如果这是一个顶级状态，比如上例中contacts没有父状态，他的父模板就为index.html
眼下，'contacts'还不能被激活，让我们看看怎么激活这个状态
有三种方式激活一个状态：
$state.go()方法Call $state.go(). 高层次的简单的方法. Learn More
ui-sref指示器中的链接 . Learn More
There are several methods for configuring a state's template.
As seen above, the simplest way to set your template is via the template config property.
- $stateProvider.state('contacts', {
- template: '<h1>My Contacts</h1>'
- })
Instead of writing the template inline you can load a partial. This is probably how you'll set templates most of the time.
- $stateProvider.state('contacts', {
- templateUrl: 'contacts.html'
- })
- $stateProvider.state('contacts', {
- templateUrl: function (stateParams){
- return '/partials/contacts.' + stateParams.filterBy + '.html';
- }
- })
- $stateProvider.state('contacts', {
- templateProvider: function ($timeout, $stateParams) {
- return $timeout(function () {
- return '<h1>' + $stateParams.contactId + '</h1>'
- }, 100);
- }
- })
<ui-view>
to have some default content before its populated by a state activation, you can do that as well. The contents will be replaced as soon as a state is activated and populates the ui-view with a template.
- <body>
- <ui-view>
- <i>Some content will load here!</i>
- </ui-view>
- </body>
You can assign a controller to your template. Warning: The controller willnot be instantiated if template is not defined.
You set your controller like this:
- $stateProvider.state('contacts', {
- template: '<h1>{{title}}</h1>',
- controller: function($scope){
- $scope.title = 'My Contacts';
- }
- })
Or if you already have a controller defined on the module, like this:
- $stateProvider.state('contacts', {
- template: ...,
- controller: 'ContactsCtrl'
- })
Or use controllerAs syntax if preferred:
- $stateProvider.state('contacts', {
- template: ...,
- controller: 'ContactsCtrl as contact'
- })
Or for more advanced needs you can use the controllerProvider to dynamically return a controller function or string for you:
- $stateProvider.state('contacts', {
- template: ...,
- controllerProvider: function($stateParams) {
- var ctrlName = $stateParams.type + "Controller";
- return ctrlName;
- }
- })
Controllers can use the $scope.on() method to listen for events fired by state transitions.
Controllers are instantiated on an as-needed basis, when their corresponding scopes are created, i.e. when the user manually navigates to a state via a URL, $stateProvider will load the correct template into the view, then bind the controller to the template's scope.
You can use resolve to provide your controller with content or data that is custom to the state. Resolve is an optional map of dependencies which should be injected into the controller.
If any of these dependencies are promises, they will be resolved and converted to a valuebefore the controller is instantiated and the $routeChangeSuccess event is fired.
The resolve property is a map object. The map object contains key/value pairs of:
Examples:
Each of the objects in resolve below must be resolved (via deferred.resolve() if they are a promise) before the controller is instantiated. Notice how each resolve object is injected as a parameter into the controller.
- $stateProvider.state('myState', {
- resolve:{
- // Example using function with simple return value.
- // Since it's not a promise, it resolves immediately.
- simpleObj: function(){
- return {value: 'simple!'};
- },
- // Example using function with returned promise.
- // This is the typical use case of resolve.
- // You need to inject any services that you are
- // using, e.g. $http in this example
- promiseObj: function($http){
- // $http returns a promise for the url data
- return $http({method: 'GET', url: '/someUrl'});
- },
- // Another promise example. If you need to do some
- // processing of the result, use .then, and your
- // promise is chained in for free. This is another
- // typical use case of resolve.
- promiseObj2: function($http){
- return $http({method: 'GET', url: '/someUrl'})
- .then (function (data) {
- return doSomeStuffFirst(data);
- });
- },
- // Example using a service by name as string.
- // This would look for a 'translations' service
- // within the module and return it.
- // Note: The service could return a promise and
- // it would work just like the example above
- translations: "translations",
- // Example showing injection of service into
- // resolve function. Service then returns a
- // promise. Tip: Inject $stateParams to get
- // access to url parameters.
- translations2: function(translations, $stateParams){
- // Assume that getLang is a service method
- // that uses $http to fetch some translations.
- // Also assume our url was "/:lang/home".
- translations.getLang($stateParams.lang);
- },
- // Example showing returning of custom made promise
- greeting: function($q, $timeout){
- var deferred = $q.defer();
- $timeout(function() {
- deferred.resolve('Hello!');
- }, 1000);
- return deferred.promise;
- }
- },
- // The controller waits for every one of the above items to be
- // completely resolved before instantiation. For example, the
- // controller will not instatiate until promiseObj's promise has
- // been resolved. Then those objects are injected into the controller
- // and available for use.
- controller: function($scope, simpleObj, promiseObj, promiseObj2, translations, translations2, greeting){
- $scope.simple = simpleObj.value;
- // You can be sure that promiseObj is ready to use!
- $scope.items = promiseObj.items;
- $scope.items = promiseObj2.items;
- $scope.title = translations.getLang("english").title;
- $scope.title = translations2.title;
- $scope.greeting = greeting;
- }
- })
Learn more about how resolved dependencies are inherited down to child states.
You can attach custom data to the state object (we recommend using a data property to avoid conflicts).
- // Example shows an object-based state and a string-based state
- var contacts = {
- name: 'contacts',
- templateUrl: 'contacts.html',
- data: {
- customData1: 5,
- customData2: "blue"
- }
- }
- $stateProvider
- .state(contacts)
- .state('contacts.list', {
- templateUrl: 'contacts.list.html',
- data: {
- customData1: 44,
- customData2: "red"
- }
- })
- function Ctrl($state){
- console.log($state.current.data.customData1) // outputs 5;
- console.log($state.current.data.customData2) // outputs "blue";
- }
Learn more about how custom data properties are inherited down to child states.
There are also optional 'onEnter' and 'onExit' callbacks that get called when a state becomes active and inactive respectively. The callbacks also have access to all the resolved dependencies.
- $stateProvider.state("contacts", {
- template: '<h1>{{title}}</h1>',
- resolve: { title: 'My Contacts' },
- controller: function($scope, title){
- $scope.title = 'My Contacts';
- },
- onEnter: function(title){
- if(title){ ... do something ... }
- },
- onExit: function(title){
- if(title){ ... do something ... }
- }
- })
All these events are fired at the $rootScope level.
- $rootScope.$on('$stateChangeStart',
- function(event, toState, toParams, fromState, fromParams){ ... })
- $rootScope.$on('$stateChangeStart',
- function(event, toState, toParams, fromState, fromParams){
- event.preventDefault();
- // transitionTo() promise will be rejected with
- // a 'transition prevented' error
- })
v0.3.0 - fired when a requested statecannot be found using the provided state name during transition. The event is broadcast allowing any handlers a single chance to deal with the error (usually by lazy-loading the unfound state). A specialunfoundStateobject is passed to the listener handler, you can see its three properties in the example. Useevent.preventDefault() to abort the transition (transitionTo() promise will be rejected with a 'transition aborted' error). For a more in-depth example on lazy loading states, seeHow To: Lazy load states
- // somewhere, assume lazy.state has not been defined
- $state.go("lazy.state", {a:1, b:2}, {inherit:false});
-
- // somewhere else
- $scope.$on('$stateNotFound',
- function(event, unfoundState, fromState, fromParams){
- console.log(unfoundState.to); // "lazy.state"
- console.log(unfoundState.toParams); // {a:1, b:2}
- console.log(unfoundState.options); // {inherit:false} + default options
- })
- $rootScope.$on('$stateChangeSuccess',
- function(event, toState, toParams, fromState, fromParams){ ... })
- $rootScope.$on('$stateChangeError',
- function(event, toState, toParams, fromState, fromParams, error){ ... })
$viewContentLoading - fired once the view begins loading,before the DOM is rendered. The '$scope' broadcasts the event.
- $scope.$on('$viewContentLoading',
- function(event, viewConfig){
- // Access to all the view config properties.
- // and one special property 'targetView'
- // viewConfig.targetView
- });
$viewContentLoaded - fired once the view is loaded,after the DOM is rendered. The '$scope' of the view emits the event.
- $scope.$on('$viewContentLoaded',