Allowed custom .js or .json file outputs with --config #75
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist
status: accepting prs
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...