Bug 1281421 - followup - fix ESLint error, even though the syntax was correct. r=me
authorMike de Boer <mdeboer@mozilla.com>
Thu, 28 Jul 2016 13:15:09 +0200
changeset 346916 705ce7870772b7d68b771edc924111cff49e3a60
parent 346915 f962e7e8fb1099c29e3ff816ff0eb0a2c8fff5df
child 346917 bc66bb60d83dd5f52e0d7143928fc4bada71ad48
push id6389
push userraliiev@mozilla.com
push dateMon, 19 Sep 2016 13:38:22 +0000
treeherdermozilla-beta@01d67bfe6c81 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersme
bugs1281421
milestone50.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1281421 - followup - fix ESLint error, even though the syntax was correct. r=me MozReview-Commit-ID: GXEEeuoqlxt
toolkit/modules/FinderIterator.jsm
--- a/toolkit/modules/FinderIterator.jsm
+++ b/toolkit/modules/FinderIterator.jsm
@@ -22,17 +22,17 @@ this.FinderIterator = {
   _catchingUp: new Set(),
   _previousParams: null,
   _previousRanges: [],
   _spawnId: 0,
   ranges: [],
   running: false,
 
   // Expose `kIterationSizeMax` to the outside world for unit tests to use.
-  get kIterationSizeMax() kIterationSizeMax,
+  get kIterationSizeMax() { return kIterationSizeMax },
 
   /**
    * Start iterating the active Finder docShell, using the options below. When
    * it already started at the request of another consumer, we first yield the
    * results we already collected before continuing onward to yield fresh results.
    * We make sure to pause every `kIterationSizeMax` iterations to make sure we
    * don't block the host process too long. In the case of a break like this, we
    * yield `undefined`, instead of a range.