angularjs – 提供者依赖注入和uglify特例
发布时间:2020-12-17 17:17:52 所属栏目:安全 来源:网络整理
导读:我使用了 angular-app的安全功能,并且在authorizationProvider中有一些时髦的东西 angular.module('security.authorization',['security.service'])// You can add them as resolves to routes to require authorization levels// before allowing a route c
我使用了
angular-app的安全功能,并且在authorizationProvider中有一些时髦的东西
angular.module('security.authorization',['security.service']) // You can add them as resolves to routes to require authorization levels // before allowing a route change to complete .provider('securityAuthorization',{ requireUser: ['securityAuthorization',function(securityAuthorization) { return securityAuthorization.requireUser(); }],$get: ['security','securityRetryQueue',function(security,queue) { var service = { requireUser: function() { //Stuff ... return true; }; return service; }] }); 提供者将自身注入属性’requireUser’,该属性调用$get工厂方法返回的函数.现在,当我尝试对此进行uglify(grunt-contrib-uglify)时,它失败了 requireUser: ['securityAuthorization',function(securityAuthorization) { return securityAuthorization.requireUser(); }] 使用未知提供者:eProvider< - e.我怎样才能缩小这个?我已经尝试了替代提供程序声明(从1.1.x开始,可以像普通工厂一样声明提供程序,即注入依赖项并让提供程序成为函数),但这也不起作用,因为它查找依赖项security.authorization模块. 解决方法
grunt-contrib-uglify的一个选项是
mangle
尝试将此添加到您的Uglify配置中: uglify: { options: { mangle: false } } (编辑:李大同) 【声明】本站内容均来自网络,其相关言论仅代表作者个人观点,不代表本站立场。若无意侵犯到您的权利,请及时与联系站长删除相关内容! |
推荐文章
站长推荐
热点阅读