chore(formatting): removed unnecessary white spaces

2014-03-08 02:01:06 +09:00
parent a86cb7d794
commit 483325a7b5
6 changed files with 18 additions and 18 deletions
@@ -11,17 +11,17 @@ var AREA_NAMES = {
 };

 function getNavGroup(pages, area, pageSorter, pageMapper) {
-  
+
  var navItems = _(pages)
    // We don't want the child to include the index page as this is already catered for
    .omit(function(page) { return page.id === 'index'; })
- 
+
    // Apply the supplied sorting function
    .sortBy(pageSorter)
- 
+
    // Apply the supplied mapping function
    .map(pageMapper)
- 
+
    .value();

  return {
@@ -176,7 +176,7 @@ module.exports = {
    //    - ngView
    //    - section "service"
    //    - $route
-    //    
+    //
    var areas = {};
    _(navPages)
      .groupBy('area')
@@ -38,12 +38,12 @@ You can also get this error if you accidentally load AngularJS itself more than
 <html ng-app>
  <head>
    <script src="angular.js"></script>
-    
+
    ...

  </head>
  <body>
-    
+
    ...

    <script src="angular.js"></script>
@@ -26,7 +26,7 @@ To make your Angular application work on IE please make sure that:
  1. You polyfill JSON.stringify for IE7 and below. You can use
     [JSON2](https://github.com/douglascrockford/JSON-js) or
     [JSON3](http://bestiejs.github.com/json3/) polyfills for this.
-     
+
     ```html
       <!doctype html>
       <html xmlns:ng="http://angularjs.org">
@@ -42,7 +42,7 @@ To make your Angular application work on IE please make sure that:
     ```

  2. add `id="ng-app"` to the root element in conjunction with `ng-app` attribute
-     
+
     ```html
       <!doctype html>
       <html xmlns:ng="http://angularjs.org" id="ng-app" ng-app="optionalModuleName">
@@ -54,7 +54,7 @@ To make your Angular application work on IE please make sure that:
     `<div ng-view>` instead), or

  4. if you **do use** custom element tags, then you must take these steps to make IE 8 and below happy:
-     
+
     ```html
       <!doctype html>
       <html xmlns:ng="http://angularjs.org" id="ng-app" ng-app="optionalModuleName">
@@ -64,7 +64,7 @@ To make your Angular application work on IE please make sure that:
               document.createElement('ng-include');
               document.createElement('ng-pluralize');
               document.createElement('ng-view');
-     
+
               // Optionally these for CSS
               document.createElement('ng:include');
               document.createElement('ng:pluralize');
@@ -79,7 +79,7 @@ To make your Angular application work on IE please make sure that:
     ```
  5. Use `ng-style` tags instead of `style="{{ someCss }}"`. The later works in Chrome and Firefox
     but does not work in Internet Explorer <= 11 (the most recent version at time of writing).
-     
+

 The **important** parts are:

@@ -165,7 +165,7 @@ In IE, the behavior is that the `BODY` element has three children:

 ## CSS Styling of Custom Tag Names

-To make CSS selectors work with custom elements, the custom element name must be pre-created with 
+To make CSS selectors work with custom elements, the custom element name must be pre-created with
 `document.createElement('my-tag')` regardless of XML namespace.

 ```html
@@ -91,7 +91,7 @@ phonecatApp.controller('PhoneListCtrl', function ($scope) {
 record. This property is used to order phones by age.

 * We added a line to the controller that sets the default value of `orderProp` to `age`. If we had
-not set a default value here, the `orderBy` filter would remain uninitialized until our 
+not set a default value here, the `orderBy` filter would remain uninitialized until our
 user picked an option from the drop down menu.

  This is a good time to talk about two-way data-binding. Notice that when the app is loaded in the
@@ -117,7 +117,7 @@ describe('PhoneCat controllers', function() {
    var scope, ctrl;

    beforeEach(module('phonecatApp'));
-    
+
    beforeEach(inject(function($controller) {
      scope = {};
      ctrl = $controller('PhoneListCtrl', {$scope:scope});
@@ -22,8 +22,8 @@ The most important changes are listed below. You can see the full diff on [GitHu
 ## Template

 The custom service is defined in `app/js/services.js` so we need to include this file in our layout
-template. Additionally, we also need to load the `angular-resource.js` file, which contains the 
-{@link api/ngResource ngResource} module and in it the {@link api/ngResource.$resource $resource} 
+template. Additionally, we also need to load the `angular-resource.js` file, which contains the
+{@link api/ngResource ngResource} module and in it the {@link api/ngResource.$resource $resource}
 service, that we'll soon use:

 __`app/index.html`.__
@@ -33,7 +33,7 @@ describe("convertDatetimeData", function() {
                  AMPMS: ['AM', 'PM'],
                  DATEFORMATS: ['a', 'b', 'c', 'd'],
                  TIMEFORMATS: ['e', 'f', 'g', 'h'] };
-                  
+
  it('should convert empty datetime obj', function() {
    var processedData = convert(dataObj);
    expect(processedData.MONTH).toEqual(['Enero', 'Pebrero']);