Skip to content

Allowed custom .js or .json file outputs with --config #75

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 5, 2019

Conversation

JoshuaKGoldberg
Copy link
Member

PR Checklist

Overview

As before, the output path defaults to --eslintrc.js. --eslint will default to --config which has that default.
The format of the output path depends on its file extension, with JavaScript for .js files and JSON otherwise.

The README.md list of flags is getting a little long so I added a quick manual table of contents. Will try to remember to split that into a separate PR...

As before, the output path defaults to `--eslintrc.js`. `--eslint` will default to `--config` which has that default.
The format of the output path depends on its file extension, with JavaScript for `.js` files and JSON otherwise.

The README.md list of flags is getting a little long so I added a quick manual table of contents. Will try to remember to split that into a separate PR...
@JoshuaKGoldberg JoshuaKGoldberg merged commit 14c42a7 into master Jul 5, 2019
@JoshuaKGoldberg JoshuaKGoldberg deleted the output-format branch July 5, 2019 17:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow configuring the output format of the ESLint configuration file
1 participant