I'd much rather have an automated way of detecting what rules should be set than an interactive way. Honestly, there's just no way we're going to get people to update every rule to export the type of information you're looking for.
I also don't think it's worthwhile to do anything of this sort prior to v1.0.0, as rule names and settings could still change, so any tool could be obsolete or create incorrect configurations. You can, of course, work on anything you want, but we're not going to be looking at anything in this regard until after v1.0.0 is released. On Thu, Mar 26, 2015 at 11:03 AM, Vladimir Starkov <[email protected]> wrote: > > It sounds like you're asking for ESLint to somehow expose its rules and > potential values? > > Does idea of interactive config creating is welcome to eslint? If so I > will create proof of concept piece of code. > > btw, I'm thinking idea of rules exposing hash with values and code samples > is good enough for implementation. It flexible, testable, exposed data can > be used for docs. And these pattern fits good in other linters as well. > What do you think, Nicholas? > > On Thursday, 26 March 2015 18:25:05 UTC+1, Nicholas Zakas wrote: >> >> 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. > -- ______________________________ 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.
