It sounds like you're asking for ESLint to somehow expose its rules and potential values? Unfortunately, that's not a very easy thing to do as it would require updating every single we have. (We don't even really have a good way of exposing possible options at this point.)
After we reach 1.0.0, I will be investigating auto-setup of rules. One possibility is to have a special ESLint mode that, instead of reporting errors, detects what is found in a specific file and uses that to create a config file. On Thu, Mar 26, 2015 at 5:39 AM, Roman Liutikov <[email protected]> wrote: > I was considering to create a tool for linters to create config file > interactively in the terminal, so this would look like this: > > $ tool eslint > > Q: Single quotesordouble quotes? > > > 'single' > "double" > > That's it. Get rules with possible values and ask with code samples. This > requires linters to be able to expose both rules and values via api. > However, after a short discussion, we thought it might be much better to > let linter do it by itself. > > I'd like to discuss this possibility. > > -- > 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. > -- ______________________________ 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.
