angularjs-1.6

We have a large Angularjs 1.6 application that has $rootscope scattered throughout the app in over 200 places in filters, services, routes, etc.. so it needs to be refactored, but I'm not sure how to know when to remove it. When is it a best practice to use $rootscope in the application? I've read everything from never, to using it for storing variables, which I assumed was for sharing data between controllers. I've since read that it's better to use factories/services for this use case instead and I also read that one valid use case is to use $rootscope as a global event bus. I didn't really

This question already has an answer here: Possibly unhandled rejection in Angular 1.6 9 answers We have a pattern for resolving promises in our Angular app that has served us well up until Angular 1.6.0: resource.get().$promise .then(function (response) { // do something with the response }, function (error) { // pass the error the the error service return errorService.handleError(error); }); And here is how we are triggering the error in Karma: resourceMock.get = function () { var deferred = $q.defer(); deferred.reject(error); return { $promise: deferred.promise }; }; Now, with the update to

I have the following code: angular .module('myApp') .directive('layout', function () { return { restrict: 'E', template: '<div ng-include="layoutCtrl.pageLayout"></div>', controller: 'LayoutController', controllerAs: 'layoutCtrl', bindToController: true, scope: { pageLayout: '=', pageConfiguration: '=', isPreview: '=' } }; }); angular .module('myApp') .controller('LayoutController', LayoutController); function LayoutController($scope, LayoutDTO, LayoutPreviewDTO) { var self = this; self.layoutDTO = LayoutDTO; self.layoutPreviewDTO = LayoutPreviewDTO; var test = $scope; if(self.isPreview) self

I'm having a massive problem with AngularJS routing. Up until recently everything has been fine with the following route: $routeProvider.when('/album/:albumId', { controller: 'albumPageController', templateUrl: 'views/album.html' }); and using the href: <a href="/#/album/{{album.id}}">Link</a> However, now all of the slashes are being encoded into %2F . So when I click the link, or type localhost:8000/#/album/1 into the browser, the URL is changed to: http://localhost:8000/#%2Falbum%2F1 I've tried several things to correct this: Using ng-href instead of href, Not using the first / (ie href="#

This question already has an answer here: Why are AngularJS $http success/error methods deprecated? Removed from v1.6? 2 answers Getting this error: angular.min.js:122 TypeError: $http.get(...).success is not a function at getUserInfo (app.js:7) at new (app.js:12) at Object.invoke (angular.min.js:43) at Q.instance (angular.min.js:93) at p (angular.min.js:68) at g (angular.min.js:60) at g (angular.min.js:61) at g (angular.min.js:61) at angular.min.js:60 at angular.min.js:21 Here is my code: var gitHub = angular.module('gitHub', []); gitHub.controller('mainController', ['$scope', '$http',