Enforce code style and code conventions

[cangoektas]

I noticed that linting is very loose. Personally I like to be forced to use a specific codestyle and follow certain coding conventions but it's also necessary when working in a team. A lot of beginners copy code snippets from all over the web too so it's very likely that their code get's inconsistent. But even for the experienced folks as the project gets bigger it's hard to manually stick to a certain style.

I also feel like this project has the potential to establish style and conventions for the entire React community. What do you guys think?

[gaearon]

Hi, we made a decision not to enforce any style. There are a couple of reasons: people have different preferences, some have styles mandated by their companies, and beginners will often copy and paste examples from the web which will be frustrating to adjust to a specific style.

We might allow adding custom lint rules in the future but this is not currently on the table.

[pjm17971]

@gaearon: That is a completely reasonable position, but I'm wondering if there's a recommended approach to develop with some organization mandated styling, without ejecting? Also, if there was someway to specify "lint strict" and have it use airbnb rules, that would work. Other than that, we just built our first app on this and it's going great! Thanks!!

[gaearon]

I think your best bet would be creating a separate ESLint config that extends the one in react-scripts/config/eslint, and running eslint explicitly pointing to that config. This would not work for the npm start-integrated linting, but you could add your own lint command. Note that we reserve the right rename/move/change ESLint config between minor versions because technically it’s private.