Upgrade eslint to version 7.1.0 #17
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
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
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.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ eslint (^6.7.2 → ^7.1.0) · Repo · Changelog
Release Notes
7.1.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 29 commits:
7.1.0Build: changelog update for 7.1.0Fix: astUtils.getNextLocation returns invalid location after CRLF (#13275)Update: padded-blocks loc position changes (refs #12334) (#13328)Fix: max-lines-per-function flagging arrow IIFEs (fixes #13332) (#13336)Update: block-spacing changed loc for extra (refs #12334) (#13314)Fix: report end loc in one-var-declaration-per-line (refs #12334) (#13326)Fix: no-new-symbol false positive with Symbol as an argument (#13337)Fix: arrow-parens no reporting for comments inside (fixes #12995) (#13312)Update: reporting location for semi-spacing (refs #12334) (#13285)Fix: fix false positives of no-new-func (#13333)Docs: Update new rules policies (#13343)Chore: correct fileoverview doc in accessor-pairs (#13335)Update: Improve report location for rest-spread-spacing (refs #12334) (#13313)Fix: Stop path analyzer on unknown nodes (#13305)Update: Improve report location for linebreak-style (refs #12334) (#13317)Docs: Document the "correct" way to build an array with values (#13246)Chore: remove checkbox from PR template prerequesites (#13330)New: no-loss-of-precision (fixes #11279) (#12747)Chore: Mark SourceCode getComments() method as deprecated (fixes #13293) (#13296)Docs: fix broken link in Node.js API docs (#13307)Sponsors: Sync README with websiteDocs: Gitter -> Discord URL (refs #13039) (#13308)Docs: improve documentation of no-return-await (#13215)Update: added typescript-eslint/recommended configs for init (#13235)Sponsors: Sync README with websiteChore: fix invalid syntax in require-await tests (#13277)Fix: remove custom plugins from replacedBy metadata (#13274)Sponsors: Sync README with websiteDepfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands