I typically use the YAML formatted config for readability, but looking through the code this doesn't appear to be supported. I would be glad to submit a PR adding support for different eslint config files and locations.
I would follow the priority order listed in the link below which is what eslint uses adding config/eslint.json to the top so existing functionality is not changed at all for anyone using both files:
I typically use the YAML formatted config for readability, but looking through the code this doesn't appear to be supported. I would be glad to submit a PR adding support for different eslint config files and locations.
I would follow the priority order listed in the link below which is what eslint uses adding
config/eslint.json
to the top so existing functionality is not changed at all for anyone using both files:Config priority: 1)
config/eslint.json
2).eslintrc.js
3).eslintrc.yaml
4).eslintrc.yml
5).eslintrc.json
The only additional change that would be required is abstracting out the config parsing to make usage of Config agnostic to the config file format.
Relevant portion of lib/runner.rb that needs changed
Additional config uses: https://github.com/appfolio/eslint-rails/search?utf8=%E2%9C%93&q=Config&type=
Additional info: https://eslint.org/docs/user-guide/configuring#configuration-file-formats