ng-app is the entrance to the entire angular application. It will find the corresponding angular module according to the name specified by ng-app. If it is inconsistent, the corresponding module cannot be found for initialization. Therefore, the root module name of the application must be consistent with the name specified by ng-app
ng-app is the entrance to the entire application, so it must be consistent with the module name of the entrance. An application can only have one and only ng-app
In an angular application, there can be multiple angular.modules. There should be one and only one angular.module whose name is consistent with the value of ng-app, otherwise it will be meaningless.
ng-app is the entrance to the entire angular application. It will find the corresponding angular module according to the name specified by ng-app. If it is inconsistent, the corresponding module cannot be found for initialization. Therefore, the root module name of the application must be consistent with the name specified by ng-app
ng-app is the entrance to the entire application, so it must be consistent with the module name of the entrance. An application can only have one and only ng-app
In an angular application, there can be multiple angular.modules. There should be one and only one angular.module whose name is consistent with the value of ng-app, otherwise it will be meaningless.
M1, M2,...,Mn may be different business modules, which can be used as an angular.module alone, and finally all are mounted under the
app
module.----------------------------------Separating line---------- ---------------------------------------
The above is automatically loaded. If you use manual loading, there is no name limit or quantity limit.
Renderingapp
The above example starts two angular apps without using thedirective.
ng-app
Thank you for your patient answers
It must be the same because this is the most important angular binding