All geek questions in one place

Advantage of angular UIRouter over ng-include?

I am wondering whether to use the UWW W550 router or just use a simple ng-include, I cannot fully understand why I would like to include the whole library through the built-in ng-include, which gives me the same functionality with less code?

Can someone explain what happened to

<div ng-if="somestate" ng-include="someview"></div>
+5
source share
1 answer

Can someone explain what happened to

 <div ng-if="somestate" ng-include="someview"></div>

It does not handle URLs in any way. You want the URL to change when you switch to a different state, and you want the state to change when the URL changes. You want you to be able to add bookmarks to the application or send the URL by e-mail and return to this page rather than the home page when you open the bookmark or link.

It also does not allow data resolution before switching to state. Both ui-router and ngRoute allow this: the state changes only when the data necessary to display this state has been successfully loaded.

This is the main task of ui-router and ngRoute. ui-router has many other useful properties, such as events when a state changes, view name, state inheritance (it is very useful to process a view consisting of several tabs, for example), etc.

+4
source

Source: https://habr.com/ru/post/1212424/

More articles:


All Articles