Open nikolay opened 8 years ago
I certainly don't want to hardcode all the different config files that we can come up with. The best solution is probably to make this configurable somehow. I am not sure how this can be done though.
I am open to hear viable solutions.
You can use rule options to make this configurable. I also agree that that's probably the best approach. .eslintrc can be JSON or YAML (though that documentation also says it's deprecated to not give it a .json
or .yaml
extension).
The plugin can't dictate what files are linted so the above solution doesn't work. However, there seems to be some new discussion in https://github.com/eslint/rfcs/pull/3 which will make this a user setting
Examples:
.babelrc
,.eslintrc
,.nsprc
,.jsinspectrc
, and so on.