-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[import/order]: Typescript path incorrect groups #1379
Comments
Same thing here ✋ . Aliased '@/paths' are considered external so I can't sort them correctly. |
same here. any help on this issue is much appreciated |
Hi ! I have the same bug on a big Typescript project. I found that this way of writing the imports works on its project :
It seems that So it seems to be a problem of tsconfig paths recognition. I tested the project with :
and this code works :
Hope it will help to fix the issue! |
I ran into a weird case of import/order with new lines between groups.
I'm using typescript & the typescript resolver (apologies, if this issue is on the resolver side, just tell me and I'll open it there).
I created a repo for this as that's simpler than trying to explain: https://github.com/tomaskallup/eslint-import-typescript-bug
Just clone,
yarn/npm install
&yarn/npm run lint
. It will report lines inatomics/box/box-article/box-article.ts
as wrong, because it assings different groups to imports of same type (they should be internal export according to documentation of the import/order rule) and the rule requires space between them.Since the imports start with '@', this might be related to #1293, but I didn't really find anything helpful to my case.
The text was updated successfully, but these errors were encountered: