From my understanding, AngularJS automatically appends "Provider" to registered providers, so it's not necessary to include it in the name when calling them. However, I'm following this convention and still encountering an issue where the console throws an
Unknown provider: ReportProviderProvider <- ReportProvider <- reportDirective
In my project, I have a service, provider, and directive all related to a feature called Report, each in their own respective files: ReportProvider.js, ReportService.js, ReportDirective.js
When attempting to use the directive, I encounter the mentioned error. Why does Angular append "Provider" to my required dependency?
angular.module('thdmaterialApp')
.provider('Report', function () {});
angular.module('thdmaterialApp')
.service('Report', function (ReportProvider) {
});
angular.module('thdmaterialApp')
.directive('report', function (ReportProvider) {} );