UI Router:
https://github.com/angular-ui/ui-router
ngMessages module:
https://docs.angularjs.org/api/ngMessages
The
Difference between :
https://github.com/angular-ui/ui-router
ngMessages module:
https://docs.angularjs.org/api/ngMessages
The
ngMessages module provides enhanced support for displaying messages within templates (typically within forms or when rendering message objects that return key/value data). Instead of relying on JavaScript code and/or complex ng-if statements within your form template to show and hide error messages specific to the state of an input field, the ngMessages and ngMessage directives are designed to handle the complexity, inheritance and priority sequencing based on the order of how the messages are defined in the template.Difference between :
From the AngularJS mailing list I got an amazing thread that explains service vs factory vs provider and their injection usage. Compiling the answers:
Services
Syntax:
Result: When declaring serviceName as an injectable argument you will be provided with an instance of the function. In other words
module.service( 'serviceName', function );Result: When declaring serviceName as an injectable argument you will be provided with an instance of the function. In other words
new FunctionYouPassedToService().Factories
Syntax:
Result: When declaring factoryName as an injectable argument you will be provided with the value that is returned by invoking the function reference passed to module.factory.
module.factory( 'factoryName', function );Result: When declaring factoryName as an injectable argument you will be provided with the value that is returned by invoking the function reference passed to module.factory.
Providers
Syntax:
Result: When declaring providerName as an injectable argument you will be provided with
module.provider( 'providerName', function );Result: When declaring providerName as an injectable argument you will be provided with
(new ProviderFunction()).$get(). The constructor function is instantiated before the $get method is called - ProviderFunction is the function reference passed to module.provider.
Providers have the advantage that they can be configured during the module configuration phase.
See here for the provided code.
Note:
http://devdactic.com/user-auth-angularjs-ionic/
https://medium.com/opinionated-angularjs/techniques-for-authentication-in-angularjs-applications-7bbf0346acec#.t17rl3b99
http://devdactic.com/user-auth-angularjs-ionic/
https://medium.com/opinionated-angularjs/techniques-for-authentication-in-angularjs-applications-7bbf0346acec#.t17rl3b99
Restricting element visibility
AngularJS comes with several directives to show or hide an element based on some scope property or expression: ngShow, ngHide, ngIf and ngSwitch. The first two will use a style attribute to hide the element, while the last two will actually remove the element from the DOM.
The first solution (hiding it) is best used only when the expression changes frequently and the element doesn’t contain a lot of template logic and scope references. The reason for this is that any template logic within a hidden element will still be reevaluated on each digest cycle, slowing down the application. The second solution will remove the DOM element entirely, including any event handlers and scope bindings. Changing the DOM is a lot of work for the browser (hence the reason for using ngShow/ngHide in some cases), but worth the effort most of the time. Since user access doesn’t change often, using ngIf or ngSwitch is the best choice:
<div ng-if="currentUser">Welcome, {{ currentUser.name }}</div>
<div ng-if="isAuthorized(userRoles.admin)">You're admin.</div>
<div ng-switch on="currentUser.role"> <div ng-switch-when="userRoles.admin">You're admin.</div> <div ng-switch-when="userRoles.editor">You're editor.</div> <div ng-switch-default>You're something else.</div> </div>
The switch example assumes a user can have only one role. I’m sure you can come up with something more flexible, but you get the idea.
Error: Cannot not user $scope in factory?
http://stackoverflow.com/questions/22159189/accessing-scope-in-angularjs-factory
You don't typically use
Error: Cannot not user $scope in factory?
http://stackoverflow.com/questions/22159189/accessing-scope-in-angularjs-factory
You don't typically use
$scope inside a factory, service or provider. Usually, you would return the promise (returned by $http) and then handle the promise in a controller (where you do have $scope).