Update eslint to version 3.12.0 🚀 #172
Closed
Conversation
This file contains 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.
Hello lovely humans,
eslint just published its new version 3.12.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of eslint.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
GitHub Release
prefer-const(fixes #7712) (#7717) (Teddy Katz)operator-linebreak(fixes #7459) (#7726) (Teddy Katz)indentoptions for array and object literals (fixes #7473) (#7681) (Teddy Katz)capitalized-comments(#7701) (Teddy Katz)package.json(#7684) (Kent C. Dodds)The new version differs by 138 commits .
da79f173.12.0519e790Build: package.json and changelog update for 3.12.0e569225Update: fix false positive/negative of yoda rule (fixes #7676) (#7695)e95a230Fix: indent "first" option false positive on nested arrays (fixes #7727) (#7728)81f9e7dFix: Allow duplicated let declarations inprefer-const(fixes #7712) (#7717)1d0d61dNew: Add no-await-in-loop rule (#7563)2cdfb4eNew: Additional APIs (fixes #6256) (#7669)4278c42Update: make no-obj-calls report errors for Reflect (fixes #7700) (#7710)4742d82Docs: clarify the default behavior ofoperator-linebreak(fixes #7459) (#7726)a8489e2Chore: Avoid parserOptions boilerplate in tests for ES6 rules (#7724)b921d1fUpdate: addindentoptions for array and object literals (fixes #7473) (#7681)7079c89Update: Add airbnb-base to init styleguides (fixes #6986) (#7699)63bb3f8Docs: improve the documentation for the autofix API (#7716)f8786fbUpdate: add fixer forcapitalized-comments(#7701)abfd24fFix: don't validate schemas for disabled rules (fixes #7690) (#7692)There are 138 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade