MD Settings: ESLint --fix output, WIP.

chrome/browser/resources/settings/people_page/lock_screen_constants.js

 // Copyright 2016 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 /**
  * @fileoverview Constants used for logging the pin unlock setup uma.
  */
 
 /**
  * Name of the pin unlock setup uma histogram.
@@ skipping 12 matching lines @@
   ENTER_PIN: 3,
   CONFIRM_PIN: 4,
   MAX_BUCKET: 5
 };
 
 cr.define('settings', function() {
 /**
  * Helper function to send the progress of the pin setup to be recorded in the
  * histogram.
  * @param {LockScreenProgress} currentProgress
  */

[dschuyler, 2017/04/19 18:58:41]

Also missed the comment indent (I assume related to the other issues with
comment indention).

[dpapad, 2017/04/19 19:19:55]

Yes, that is the same issue mentioned before.

-var recordLockScreenProgress = function(currentProgress) {
-  if (currentProgress >= LockScreenProgress.MAX_BUCKET) {
-    console.error('Expected a enumeration value of ' +
+  var recordLockScreenProgress = function(currentProgress) {
+    if (currentProgress >= LockScreenProgress.MAX_BUCKET) {
+      console.error('Expected a enumeration value of ' +
         LockScreenProgress.MAX_BUCKET + ' or lower: Received ' +
         currentProgress + '.');
-    return;
-  }
-  chrome.send('metricsHandler:recordInHistogram',
+      return;
+    }
+    chrome.send('metricsHandler:recordInHistogram',
       [PinUnlockUmaHistogramName, currentProgress,
-       LockScreenProgress.MAX_BUCKET]);
-};
+        LockScreenProgress.MAX_BUCKET]);
+  };
 
   return {
     recordLockScreenProgress: recordLockScreenProgress
   };
 });