Case-insensitive sort of named imports
See original GitHub issue👋 @lydell!
After switching from TSLint to ESLint and your plugin, I’ve noticed that named imports are sorted differently. Your approach is case-sensitive, while TSLint’s ordered-imports
is not by default.
// tslint
import { a, B, c } from "somethiing";
// eslint-plugin-simple-import-sort
import { B, a, c } from "somethiing";
The former notation feels more natural to me. WDYT?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:6
- Comments:18 (8 by maintainers)
Top Results From Across the Web
"Sort import statements" should be case-insensitive : PY-20159
It appears that the order of import statements themselves is always case-insensitive, but at the same time names inside "from" imports are sorted...
Read more >How to sort import statements in Eclipse in case insensitive ...
Select your imports, right click, choose Sort, case-insensitive. Not sure how you would automate it, but it's got to be better than manual....
Read more >Rule: ordered-imports - Palantir Open Source
The exact ordering can be controlled by the named-imports-order option. ... "case-insensitive' : Correct order is "Bar" , "baz" , "Foo" .
Read more >sort-imports - ESLint - Pluggable JavaScript Linter
When true the rule ignores the case-sensitivity of the imports local name. ... Default is false . ignoreDeclarationSort. Ignores the sorting of import...
Read more >Sort data in a range or table - Microsoft Support
How to sort and organize your Excel data numerically, alphabetically, by priority or ... You might want to arrange a list of names...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Released in v4.0.0. Thank you everyone for the great discussion!
In my opinion one of the benefits of this package is that it has no options. I’d like to keep it like that until an option is absolutely necessary. Convince me and we’ll change this!