Update dependency eslint-plugin-simple-import-sort to v13#1964
Open
renovate[bot] wants to merge 2 commits into
Open
Update dependency eslint-plugin-simple-import-sort to v13#1964renovate[bot] wants to merge 2 commits into
renovate[bot] wants to merge 2 commits into
Conversation
230c8ab to
2fc6a97
Compare
|
All alerts resolved. Learn more about Socket for GitHub. This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. |
2042241 to
b883dfd
Compare
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
edb5ec0 to
429b5b8
Compare
6835033 to
8aa3ba5
Compare
8aa3ba5 to
649520a
Compare
9e7f842 to
bad9b52
Compare
740a726 to
c9ce776
Compare
d3404a5 to
0eed05e
Compare
- force AGP 9 to act like AGP 8 until libs migrated - add TODO to revert both flags and old KGP once ecosystem ready - ref: react/react-native#56222
0eed05e to
92cbfab
Compare
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.
This PR contains the following updates:
9.0.0β13.0.0Release Notes
lydell/eslint-plugin-simple-import-sort (eslint-plugin-simple-import-sort)
v13.0.0Compare Source
This release puts imports from the same source, but with different import styles, in a deterministic order.
That is especially useful if you need to have both a namespace import and want to import a few things separately (since that cannot be combined into a single import statement). With the above rule, the imports end up in a deterministic order.
Itβs only a breaking change if you import from the same source multiple times in the same file (using different styles), and only in the form that you need to autofix your files.
Thanks to Kannan Goundan (@βcakoose)!
v12.1.1Compare Source
This release adds a short
meta.docs.descriptionto each rule. Thanks to fisker Cheung (@βfisker)!v12.1.0Compare Source
This release adds TypeScript type definitions for the plugin itself. This is useful when you use TypeScript to check your ESLint configuration. It assumes that you install
@types/eslintyourself. Thanks to @βLogicer16!v12.0.0Compare Source
This release removes the support for import assignments added in version 11.0.0:
If you miss the support for import assignments, I suggest you write your own ESLint rule which moves them out of the way from the actual imports, sorting them or not.
v11.0.0Compare Source
This release adds support for TypeScript import assignments (
import A = B.Candimport A = require("module")). Thanks to Szabolcs Kurdi (@βszku01) and Svyatoslav Zaytsev (@βMillerSvt)!Itβs only a breaking change if you use TypeScript import assignments, and only in the form that you need to autofix your files.
In other news, this release adds the
metaplugin property in preparation for ESLint Flat Config, and avoids the deprecatedcontext.getSourceCode()method (while still being backwards compatible).v10.0.0Compare Source
This release might move some imported items with
typearound. This is a breaking formatting change (that only affects TypeScript and Flow), but only in the form of that you need to autofix your files.In previous versions,
typespecifiers came first:Now, all specifiers are sorted alphabetically, regardless of
type:Motivation:
You might import a class for a type annotation using:
Later, you also start instantiating that class in the same file (
new MyClass()), so you removetype.Previously, this resulted in a messy diff due to the class moving:
import { - type MyClass, coolFunction, + MyClass, } from "example";Now, the sorting with the
typekeyword would be:Now thereβs no reordering diff, just the
typekeyword being removed:import { coolFunction, - type MyClass, + MyClass, } from "example";This is consistent with [βWhy sort on
from?β][sort-from].Thanks to Jake Bailey (@βjakebailey) for reporting and suggesting the fix!
Configuration
π Schedule: (in timezone Europe/London)
π¦ Automerge: Disabled by config. Please merge this manually once you are satisfied.
β» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
π Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.