-
-
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
[no-internal-modules] Extract violation types to options #2213
Comments
Can you elaborate as to why? also, why you can't use |
Ok, sorry i will provide more context:
Without this custom aliases are treated as unresolved, but with this configured I think it is useful to allow deep relative paths like Unfortunately i cannot use e.g. eslint-plugin-import/src/rules/no-internal-modules.js Lines 58 to 70 in 1359e24
eslint-plugin-import/src/rules/no-internal-modules.js Lines 90 to 91 in 1359e24
|
I agree with @ppapla, it would be nice to have a way to allow this for relative imports. That would help with folks moving from tslint's |
Hi, I'm wondering if
potentialViolationTypes
can be set from rule options, because I would like to apply this rule only toexternal
,internal
import and not e.g.sibling
,parent
.eslint-plugin-import/src/rules/no-internal-modules.js
Line 125 in 1359e24
The text was updated successfully, but these errors were encountered: