Very nice. Based on the open tickets, and roadmap, we are getting close to 0.2.0. Could we update (or rather add to the roadmap) a few things?
* I'm still very interested in context identifiers for different frameworks. While I think that adding framework specific rules to the main distribution is not necessary, being able to detect framework and then run custom rules could be incredibly powerful thing that is not covered by any linting tool currently available. * Ability to disable rules per line * More complicated selectors for rules (cssauron, esquery/esdispatch, etc.) * More rules (and definitions for what they should be/do) * Ability to not only define global variables, but declaring dependency on another file * Something to make adding custom rules easier (maybe through npm or something else) * Performance (I finally was able to run the code through the profiler for the first time yesterday, or rather, I finally was able to find a full fledged profiler for Node.js) * A way to output results to a file, instead of command line Thanks, Ilya Volodin On Thursday, December 5, 2013 9:10:36 PM UTC-5, Nicholas Zakas wrote: > Hi all, > > Just a heads up to say that I've published a new version to npm. This > includes a number of bug fixes. The complete changelog is here: > > https://github.com/nzakas/eslint/commit/f88445d5c27827711f10e6c75f5d8139bfc6ce49 > > Thanks for all the hard work! We're making a ton of progress. > > -- > > ______________________________ > 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/groups/opt_out.
