Use explicit dependency injection annotation in controllers with strict DI enabled

Don't inject invalid dependencies in directives

Number of injected dependencies matches the number of function parameters in directives

Use explicit dependency injection annotation in directives with strict DI enabled

Don't inject invalid dependencies in filters

Number of injected dependencies matches the number of function parameters in filters

Use explicit dependency injection annotation in filters with strict DI enabled

Don't inject invalid dependencies in services

Number of injected dependencies matches the number of function parameters in services

Use explicit dependency injection annotation in services with strict DI enabled

Use explicit dependency injection annotation in factories with strict DI enabled

Route refers to a known controller

Use built-in AngularJS directives whenever possible

Always have . in ngModel

Binding refers to a known property

Use explicit dependency injection annotation in controllers with strict DI enabled

When bootstrapping application in strict DI mode, use explicit annotation to inject dependencies in controllers

CheckId	NG1010404
TypeName	UseExplicitDependencyInjectionAnnotationWithStrictDiEnabledInControllers
Severity	CriticalError
Type	Controller

Resolution

When bootstrapping application in strict DI mode, you have to use explicit annotation to inject dependencies in controllers. Without it, your application will break on runtime.

Bad practice (no explicit annotation used for injecting dependencies into a controller used in an application bootstrapped in strict DI mode)

angular
    .module('app')
    .controller('HomeController', function($scope) {
        $(".search-details-form").hide();
    });

angular.bootstrap(document, ['app'], {
    strictDi: true
});

Good practice

angular
    .module('app')
    .controller('HomeController', ['$scope', function($scope) {
        $(".search-details-form").hide();
    }]);

angular.bootstrap(document, ['app'], {
    strictDi: true
});

Message Suppression

SharePoint Customization Analysis Framework (SPCAF), 7.15.0.0

Disclaimer: The views and opinions expressed in this documentation and in SPCAF do not necessarily reflect the opinions and recommendations of Microsoft or any member of Microsoft. SPCAF and RENCORE are registered trademarks of Rencore. All other trademarks, service marks, collective marks, copyrights, registered names, and marks used or cited by this documentation are the property of their respective owners.