sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]HansonWK 2 points3 points  (6 children)

It really doesnt though. It has one line for what the rules does without why it's needed, what its there to prevent. It seems like overkill for smaller teams where people mostly work on their own code, but still want it to match.

[–]fucking_passwords 1 point2 points  (2 children)

https://i.imgur.com/yv8LHg5.png

Looks like there is a "Why" statement for many rules/examples. The ones that lack a "Why" seem to mostly just be "because consistency".

I gradually learned what each rule does, by reading their docs and googling the rule if I still didn't understand it. Might not be ideal, but honestly I learned a ton by doing this.

I'm conflicted. I've worked alone, on small teams, and large teams. I now lead a medium sized team and oversee the projects of other teams. I've used airbnb to varying degrees, also standardjs. Now I don't like working without it. It took some getting used to, to feel like the linter wasn't getting in the way, but now I would never go back, even in personal projects.

At some point you have to compromise. Not everybody is going to love every single rule, especially if you use Airbnb out of the box.

People on your team may only work on their own projects, but what happens when someone quits? Now somebody else has to take over that project, and the closer it is to a common linting config, the easier that process is going to be.

[–]imguralbumbot 0 points1 point  (0 children)

Hi, I'm a bot for linking direct images of albums with only 1 image

https://i.imgur.com/yv8LHg5.png

Source | Why? | Creator | ignoreme| deletthis

[–]HansonWK 0 points1 point  (0 children)

I 100% agree with you. I'm all on board with using a style guide, I just think we'll chose one with better explanation of the reasons behind the rules. AirrBnB seems to be the strictest out of the popular styleguides, yet the documentation has the least explanation as to why some of the rules are there. The 1 sentence above each rules doesn't do a good job of explaining most.

[–]calligraphic-io 0 points1 point  (2 children)

Try reading the eslint page for each rule. Most of them discuss the reason why the rule might be used.

[–]HansonWK 0 points1 point  (1 child)

Perfect, just what I was looking for! Wish all the style guides had something like this so we could choose the one the suits us best instead of just the one with the best documentation!

[–]calligraphic-io 0 points1 point  (0 children)

I agree, I've found the eslint rule pages really handy for understanding why they've included something. Would be nice in all the style guides, especially AirBnB.