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.
