Sooooo that init command. I totally missed it. Not even remotely gonna lie. Feel like a dufus though. And in fact I'm gonna go try it out now.
On Thu, 9 Jun 2016, 15:37 Burak Yiğit Kaya, <[email protected]> wrote: > Oh my, how embarrassing for me to forget us doing this already :( > > I was also thinking putting this on the main page and may be even with an > animated gif showing the init steps on the main page (both eslint.org and > the repo's readme on GitHub). > > On Thu, Jun 9, 2016 at 3:50 PM Ilya Volodin <[email protected]> wrote: > >> We already do. First question asks if you want to use popular preset or >> answer question about your style or inspect your files to autodetect your >> style. If you go with popular preset, we list Standard, AirBnB and Google. >> I think the problem in this case is that Rijnhard didn’t find information >> about init command itself, and as such, didn’t see those presets. While our >> “Get started” button on the site is very visible and up front, maybe we >> should replace it with minimal set of instructions right on the homepage? >> Most of the NPM packages do that. Something like: >> >> “npm install –g ESLint” >> >> “eslint –init” >> >> “eslint .” >> >> >> >> Thanks, >> >> >> >> Ilya Volodin >> >> >> >> *From:* [email protected] [mailto:[email protected]] *On >> Behalf Of *Burak Yigit Kaya >> *Sent:* Thursday, June 9, 2016 5:55 AM >> *To:* Rijnhard <[email protected]>; ESLint < >> [email protected]> >> *Subject:* Re: [ESLint] My experience configuring ESlint >> >> >> >> Hi Rijnhard, >> >> thank you very much for taking the time to share your experience with us. >> I think there are lots of useful information in your e-mail and I think >> based on our bandwidth we may be able to address some of them. >> >> Ilya - I'm thinking may be we can incorporate downloading/mentioning some >> popular presets into `eslint --init`. What do you think? >> >> On Thu, Jun 9, 2016 at 11:12 AM Rijnhard <[email protected]> >> wrote: >> >> Hi >> >> >> >> So firstly (like a child) I got annoyed and tweeted about my experience >> configuring ESLint. >> >> >> >> My only frame of reference is configuring JSHint about a day ago, and >> here are some of my experiences. >> >> >> >> Your documentation on the individual rules is exquisite, seriously >> perfect amount of detail to provide clarity and not pointlessly verbose to >> make me skim over the wrong parts, missing the bits I want to read. I am >> about halfway reading through ALL the rules and I haven't yet had a single >> issue. >> >> >> >> So where are the issues? >> >> Firstly for the life of me I couldn't find an example configuration file >> with the structure of the configuration options (I mean like "env", >> "parser", "parserOptions") I ended up stumbling upon an example on stack >> overflow, and from that I discovered that you have plugins (not even >> joking) and on the official docs you only mention how to write plugins, not >> how to use them or which ones exist. >> >> >> >> Lastly. Presets. eslint:recommended is decent for a start, but honestly >> it's pretty minimal. I know you support shareable configs, which is great, >> but that doesn't help me find one that suits what i want, or what the big >> players in the industry are advocating like Mavens style guide in Java, >> PSR-1&2 in PHP etc. >> >> >> >> To come to the actual point the main issue I have is that I have to read >> through all the rules, and there's a shit load, in order to get the >> configuration I want. And who am I to decide that this is a good >> configuration? I F**king hate node in many cases (it's like a passionate >> destructive relationship) and the only purposely opinionated "preset" is >> standard, and that should die in the hole it crawled out from. >> >> >> >> Let me stop ranting a bit, beginners, or ideally the industry would like >> more opinionated "presets" like standard, but dear god not standard. I'd >> rather castrate my only son then use that. >> >> >> >> This is what I see happening for beginners, install ESLint, pick presets >> "eslint:recommended", "standard" (but not standard, alternatives plox) and >> then only modify a few settings (mainly for project specific allowances >> like allowing console in cli applications) and go. >> >> >> >> Discovery and visibility is the problem here. And of course laziness, but >> that drives the human race so it's moot. >> >> >> >> Rant over. >> >> >> >> Thank you for providing a tool thats this powerful and configurable, is >> truly amazing. >> >> >> >> -- >> 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. >> >> -- >> 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. >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "ESLint" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/eslint/nz4o2mt7xQM/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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.
