-
-
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
Paths having more than two constructs ../ #2662
Comments
This comment was marked as spam.
This comment was marked as spam.
I'm confused; your code snippet fails to parse because you have two imports of |
Additionally, you've configured alphabetical sorting, so |
This is the code that passes the test case (with the duplicate import { helpers } from 'path/path/path/helpers';
import { cfg } from 'path/path/path/src/Cfg';
import { tip } from 'path/path/tip';
import { l10n } from 'path/src/l10n';
import { component } from '../../../../path/path/path/component';
import { controller } from '../../../../path/path/path/controller'; What about that isn't correct for you? |
Yes, it was an example |
Hm... It's strange. With these options, I have a "Reality" case, which I cited in the description |
Oh, i'm sorry. I misspelled the regex for "import/internal-regex". Thx! Expectation: import { Service } from './path/Service';
import { Controller } from '../../../../path/Controller';
import { DisplayMode } from '../../../../path/DisplayMode';
import { Location } from '../../../../path/Location'; Reality: import { Controller } from '../../../../path/Controller';
import { DisplayMode } from '../../../../path/DisplayMode';
import { Location } from '../../../../path/Location';
import { Service } from './path/Service'; I know alphabetical sorting puts special characters above letters. Is it possible to somehow change this behavior? |
You might be referring to a regression described in #2682. |
Hello! I have the following problem: when trying to sort, those paths that have more than two "../" constructs do not fall into the parent category, but fall into the internal. How to solve this problem?
Expectation:
Reality:
Config:
The text was updated successfully, but these errors were encountered: