Consider making eslint configuration inclusive

[kettanaito]

Hi!

The problem

Right now, our eslint configuration tries to lint everything in the repo. Not sure why, it just does. I've encountered multiple occasions where it attempted to lint JSON files (#24) and other build artifacts that I don't even normally have in the repo (#34).

I come to believe that the way we have eslint setup is "validate all, ignore these" instead of "validate these, ignore all".

The proposal

Let's see if we can make the eslint config inclusive instead. My reasoning is this:

• It's much easier to predict which files we want to lint than those we don't. Files like JS/TS modules are expected, so they are nice to have in the include pattern.
• Inclusive nature would prove for a more resilient config that suits more people.

The how's

Frankly, I don't know how to do this and whether this is possible with eslint. I've not used it in some time now. I cannot say that I enjoy the current configuration experience as there doesn't appear to be a way to override configs, especially when using third-party configs like this one. Overall, just not my cup of coffee when it comes to configuration design (I also believe that most linting has little practical value but this is highly subjective and I digress).

[kentcdodds]

I've not really experienced the same thing you have with not being able to override configs. It seems that I have been able to disable rules as needed, even for specific files or directories, which is why I think having a config like this is nice because it's still fully customizable. I'm happy to take a look at a reproduction if you're not able to get overrides working properly though.