issue #46: new module created just for the service API

build/loading-bar.css

@@ -1,5 +1,5 @@
 /*! 
- * angular-loading-bar v0.4.0
+ * angular-loading-bar v0.4.1
  * https://chieffancypants.github.io/angular-loading-bar
  * Copyright (c) 2014 Wes Cruver
  * License: MIT

build/loading-bar.js

@@ -1,5 +1,5 @@
 /*! 
- * angular-loading-bar v0.4.0
+ * angular-loading-bar v0.4.1
  * https://chieffancypants.github.io/angular-loading-bar
  * Copyright (c) 2014 Wes Cruver
  * License: MIT
@@ -19,17 +19,17 @@
 
 'use strict';
 
-// Alias the loading bar so it can be included using a simpler
-// (and maybe more professional) module name:
-angular.module('angular-loading-bar', ['chieffancypants.loadingBar']);
+// Alias the loading bar for various backwards compatibilities since the project has matured:
+angular.module('angular-loading-bar', ['cfp.loadingBarInterceptor']);
+angular.module('chieffancypants.loadingBar', ['cfp.loadingBarInterceptor']);
 
 
 /**
  * loadingBarInterceptor service
  *
  * Registers itself as an Angular interceptor and listens for XHR requests.
  */
-angular.module('chieffancypants.loadingBar', [])
+angular.module('cfp.loadingBarInterceptor', ['cfp.loadingBar'])
   .config(['$httpProvider', function ($httpProvider) {
 
     var interceptor = ['$q', '$cacheFactory', '$timeout', '$rootScope', 'cfpLoadingBar', function ($q, $cacheFactory, $timeout, $rootScope, cfpLoadingBar) {
@@ -145,18 +145,19 @@ angular.module('chieffancypants.loadingBar', [])
     }];
 
     $httpProvider.interceptors.push(interceptor);
-  }])
-
-
-  /**
-   * Loading Bar
-   *
-   * This service handles adding and removing the actual element in the DOM.
-   * Generally, best practices for DOM manipulation is to take place in a
-   * directive, but because the element itself is injected in the DOM only upon
-   * XHR requests, and it's likely needed on every view, the best option is to
-   * use a service.
-   */
+  }]);
+
+
+/**
+ * Loading Bar
+ *
+ * This service handles adding and removing the actual element in the DOM.
+ * Generally, best practices for DOM manipulation is to take place in a
+ * directive, but because the element itself is injected in the DOM only upon
+ * XHR requests, and it's likely needed on every view, the best option is to
+ * use a service.
+ */
+angular.module('cfp.loadingBar', [])
   .provider('cfpLoadingBar', function() {
 
     this.includeSpinner = true;

src/loading-bar.js

@@ -13,17 +13,17 @@
 
 'use strict';
 
-// Alias the loading bar so it can be included using a simpler
-// (and maybe more professional) module name:
-angular.module('angular-loading-bar', ['chieffancypants.loadingBar']);
+// Alias the loading bar for various backwards compatibilities since the project has matured:
+angular.module('angular-loading-bar', ['cfp.loadingBarInterceptor']);
+angular.module('chieffancypants.loadingBar', ['cfp.loadingBarInterceptor']);
 
 
 /**
  * loadingBarInterceptor service
  *
  * Registers itself as an Angular interceptor and listens for XHR requests.
  */
-angular.module('chieffancypants.loadingBar', [])
+angular.module('cfp.loadingBarInterceptor', ['cfp.loadingBar'])
   .config(['$httpProvider', function ($httpProvider) {
 
     var interceptor = ['$q', '$cacheFactory', '$timeout', '$rootScope', 'cfpLoadingBar', function ($q, $cacheFactory, $timeout, $rootScope, cfpLoadingBar) {
@@ -139,18 +139,19 @@ angular.module('chieffancypants.loadingBar', [])
     }];
 
     $httpProvider.interceptors.push(interceptor);
-  }])
-
-
-  /**
-   * Loading Bar
-   *
-   * This service handles adding and removing the actual element in the DOM.
-   * Generally, best practices for DOM manipulation is to take place in a
-   * directive, but because the element itself is injected in the DOM only upon
-   * XHR requests, and it's likely needed on every view, the best option is to
-   * use a service.
-   */
+  }]);
+
+
+/**
+ * Loading Bar
+ *
+ * This service handles adding and removing the actual element in the DOM.
+ * Generally, best practices for DOM manipulation is to take place in a
+ * directive, but because the element itself is injected in the DOM only upon
+ * XHR requests, and it's likely needed on every view, the best option is to
+ * use a service.
+ */
+angular.module('cfp.loadingBar', [])
   .provider('cfpLoadingBar', function() {
 
     this.includeSpinner = true;

test/loading-bar-interceptor.coffee

@@ -356,3 +356,36 @@ describe 'loadingBarInterceptor Service', ->
 
     $timeout.flush()
 
+
+describe 'LoadingBar only', ->
+  cfpLoadingBar = $document = $timeout = null
+
+  beforeEach ->
+    module 'cfp.loadingBar'
+
+    inject (_$http_, _$httpBackend_, _$document_, _$timeout_, _cfpLoadingBar_) ->
+      $timeout = _$timeout_
+      $document = _$document_
+      cfpLoadingBar = _cfpLoadingBar_
+
+  it 'should be capable of being used alone', ->
+    # just a simple quick test to make sure:
+    cfpLoadingBar.start()
+    $timeout.flush()
+
+    # test setting progress
+    cfpLoadingBar.set(0.4)
+    expect(cfpLoadingBar.status()).toBe 0.4
+
+    # make sure it was injected into the DOM:
+    expect(isLoadingBarInjected($document.find(cfpLoadingBar.parentSelector))).toBe true
+
+    cfpLoadingBar.set(0.9)
+    expect(cfpLoadingBar.status()).toBe 0.9
+
+    # test the complete call, which should remove it from the DOM
+    cfpLoadingBar.complete()
+    $timeout.flush()
+    expect(isLoadingBarInjected($document.find(cfpLoadingBar.parentSelector))).toBe false
+
+