I have been working on an Angular application for sometime now and I have started to like this approach to client-side development. It's a different approach when compared to developing applications using Backbone and Require. I was looking at routing in Angular and came across the 'resolve' property which can be used to resolve services before instantiating the Controller and it's corresponding template i.e. the domain models that are required for the View components are resolved first.
Look at a scenario where you are using a Search service to get a collection of objects that contain the search string. You can specify the route which will display the search results. When only the template and controller properties are specified, both are instantiated and the ng-view is updated with the specified template. The controller would specify dependency on the SearchService,use this service to query the back-end and then update one of the $scope variables with the response data.
While the SearchService is fetching results, you would see that the template being displayed inside the ng-view container with template variables and the same getting updated when the service returns data. This is not ideal; the search results should be available before you load the controller; and the template should display data instead of showing template variables. The 'resolve' property in the $routeProvider mentions a set of promises that should be resolved before instantiating the controller and the template. Only when all the promises are resolved, the controller and the template are instantiated. Also the promise reference is injected into the controller as a dependency. Using this promise one can directly update the values in the template instead of sending a request to the Search service.
Here's the code for the routeProvider :
Here the route '/search/:searchString', specifies the 'resolve' object which includes a promise - 'searchResults'. It queries the searchService and returns a promise. When the service is resolved the Controller - 'searchController' and the template - 'partials/search.html' are instantiated. The Controller gets the promise object:
Notice that the promise - 'searchResults' is injected into the Controller and it contains the response data. This can then be used to render the template.
Look at a scenario where you are using a Search service to get a collection of objects that contain the search string. You can specify the route which will display the search results. When only the template and controller properties are specified, both are instantiated and the ng-view is updated with the specified template. The controller would specify dependency on the SearchService,use this service to query the back-end and then update one of the $scope variables with the response data.
While the SearchService is fetching results, you would see that the template being displayed inside the ng-view container with template variables and the same getting updated when the service returns data. This is not ideal; the search results should be available before you load the controller; and the template should display data instead of showing template variables. The 'resolve' property in the $routeProvider mentions a set of promises that should be resolved before instantiating the controller and the template. Only when all the promises are resolved, the controller and the template are instantiated. Also the promise reference is injected into the controller as a dependency. Using this promise one can directly update the values in the template instead of sending a request to the Search service.
Here's the code for the routeProvider :
Here the route '/search/:searchString', specifies the 'resolve' object which includes a promise - 'searchResults'. It queries the searchService and returns a promise. When the service is resolved the Controller - 'searchController' and the template - 'partials/search.html' are instantiated. The Controller gets the promise object:
Notice that the promise - 'searchResults' is injected into the Controller and it contains the response data. This can then be used to render the template.
This is something I'm not familiar with - if searchService.getSearchResults returns a promise, and that promise is resolved before being injected (as per the resolve contract), why is the data with which the promise was resolved under .data? Or is this your model, the resolved value is {data:[results]}?
ReplyDeletethe http response object constructed contains four properties - 'data' (response data), 'config', 'status', 'statusText' and 'headers'. In this case to refer to the response data, response.data should be used. Alternatively you can write a httpInterceptor and return response.data as response.
ReplyDeleteAh, so you're resolving the promise with the response object from $http? I would usually have a specific property on my response, for example {results: []}, and then resolve with "response.data.results". Most times, I even like to verify the `results` key exists, and will reject the promise if it doesn't (regardless of response status code), just to be extra safe that the promise was resolved with the data I actually want.
ReplyDeleteDo you need to write your case brief soon? Check this out if you want to get some writing tips
ReplyDeleteThis post very useful for enhancing my knowledge. I got huge information in this post. Thank you!!!
ReplyDeleteTableau Training in Chennai
Tableau Course in Chennai
Excel Training in Chennai
Corporate Training in Chennai
Pega Training in Chennai
Power BI Training in Chennai
Embedded System Course Chennai
Linux Training in Chennai
Tableau Training in Chennai
Tableau Course in Chennai
I feel satisfied to read your blog, you have been delivering a useful & unique information to our vision.keep blogging.
ReplyDeleteRegards,
ccna Training in Chennai
ccna course in Chennai
PHP Training in Chennai
ReactJS Training in Chennai
ccna course in chennai
ccna training in chennai