Custom eslint rules

[kooparse]

It is perhaps preferable to wait the plugin model (#30).

[caoyangs]

You probably don't need to change this.

[kooparse]

You are right 👍

[jchip]

Thanks for the PR. The general approach is good. If CWD/.eslintrc and CWD/test/.eslintrc exist, then use those instead of the ones in the archetype.

Eventually these are all the eslint check scripts

https://github.com/electrode-io/electrode-archetype-react-app/blob/master/arch-gulpfile.js#L189-L192

One of the things I was considering is to allow apps to override archetype config.

https://github.com/electrode-io/electrode-archetype-react-app/blob/master/config/archetype.js

[kooparse]

In most cases, people are using only one linter config file (I think). But sure, if you want I could check for CWD/.eslintrc-react, CWD/.eslintrc-react-test, CWD/.eslintrc-node, CWD/.eslintrc-mocha-test custom files instead.
Yes, allowing apps to override the archetype config would be great, I will try to make a PR on that. :)

[citelao]

Since eslint --init can generate files like .eslintrc.json, can this accept:

1. no extension
2. .js
3. .json?

[citelao]

@kooparse +1 on separate configuration files, esp. since the archetype has the separation anyway.

However, ESLint doesn't support globbing/custom directories for .eslintrcs. It's in an issue right now. In order to get linting working in-editor (eg with Sublime-Linter), the only way is to place separate .eslintrcs in each directory:

• / for the main/client-centric .eslintrc
• /server/ for server-side
• /test/client/ for client tests
• /test/server/ for server tests

I've tested such placement (one .eslintrc in each folder as mentioned) and it works correctly in Sublime. Perhaps grab from these locations rather than by filename? IMO custom .eslintrc names are less helpful, since they can't work in editors (and won't be detected automatically in general).