Thanks Nicholas, I've created https://github.com/eslint/eslint/issues/5860
On Thursday, April 14, 2016 at 1:42:36 PM UTC-5, Nicholas Zakas wrote: > > Hi Brian, > > Please open an issue on GitHub. This should be easy enough to do. > > -N > > On Thu, Apr 14, 2016 at 11:26 AM, Brian Dukes <[email protected] > <javascript:>> wrote: > >> I'm excited to see the news that JSCS will be joining the ESLint team, >> it'll be great to have y'all spending your efforts in the same direction. >> >> We've just gone through the exercise on our team of setting standards, >> and decided to use ESLint for "correctness" rules, but used JSCS for >> formatting rules because we liked the clarity of its default reporter. Are >> there any thoughts about migrating that over as part of the transition? >> >> For example: >> >> All identifiers must be camelCase or UPPER_CASE at >> C:\inetpub\wwwroot\site.local\JavaScript\BaseLocator.js : >> 66 | this._noLocationSpan = value; >> 67 | }, >> 68 | get_instructionSpan: function() { >> ------------^ >> 69 | return this._instructionSpan; >> 70 | }, >> >> Thanks! >> >> -- >> You received this message because you are subscribed to the Google Groups >> "ESLint" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > > ______________________________ > Nicholas C. Zakas > @slicknet > > Author, Professional JavaScript for Web Developers > Buy it at Amazon.com: > http://www.amazon.com/Professional-JavaScript-Developers-Nicholas-Zakas/dp/1118026691/ref=sr_1_3 > -- You received this message because you are subscribed to the Google Groups "ESLint" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
