<div dir="ltr">Could we run eslint on the post-processed files? It's not ideal but I suspect it will still take some time to get rid of all preprocessing, and not covering browser.js in the meantime would be a bummer.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 27, 2015 at 2:10 PM, Felipe G <span dir="ltr"><<a href="mailto:felipc@gmail.com" target="_blank">felipc@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Thu, Nov 26, 2015 at 8:55 PM, Mark Banner <span dir="ltr"><<a href="mailto:mbanner@mozilla.com" target="_blank">mbanner@mozilla.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span>
</span>I did a quick test. Just looking at the browser/ directory, I set up
a minimal .eslintrc in it with just enabling most of the es6 rules.
Here's what I found in the test:<br>
<ul>
<li>316 problems were referenced. Of these, approximately (I'm
counting based on the error messages):</li>
<ul>
<li>64 files failed due to preprocessing requirements, we'd
probably just want to .eslintrcignore these for now.<br>
</li>
<li>A lot (> 120, maybe the majority of the rest), failed due
to yield statements being within functions not designated as
generator functions. That doesn't seem to cause problems, but
it appears to be wrong according to the es6.<br></li></ul></ul></div></blockquote><div><br></div></span><div>Could you post the output log somewhere? I'm sure people would volunteer to start fixing these warning and errors ahead of time :)<span class="HOEnZb"><font color="#888888"><br></font></span></div><span class="HOEnZb"><font color="#888888"><div><br><br></div><div>Felipe<br></div></font></span></div></div></div>
</blockquote></div><br></div>