Preparing for ESLint 1.0.0 which disables all rules by default#4
Open
dominicbarnes wants to merge 1 commit intomasterfrom
Open
Preparing for ESLint 1.0.0 which disables all rules by default#4dominicbarnes wants to merge 1 commit intomasterfrom
dominicbarnes wants to merge 1 commit intomasterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In the current ESLint, some rules are engaged by default. As of 1.0.0 coming up soon, the default behavior will be the same as the
--resetCLI flag, which is to disable all rules. (making everything opt-in)I've used the migration guide to make these changes:
I would like to merge this and bump to
0.1.0so I can start experimenting with the ESLint release candidates.