no-relative-parent-imports over-reporting when import/resolver = typescript
#1.392 geöffnet am 22. Juni 2019
Repository-Metriken
- Stars
- (4.946 Stars)
- PR-Merge-Metriken
- (Durchschn. Merge 138T 22h) (3 gemergte PRs in 30 T)
Beschreibung
I have been using the following tslint rule:
"no-relative-imports": [true, "allow-siblings"],
to forbid any relative imports such as import constants from '../constants'
I am trying to migrate my tslint rules to eslint, and it seems like the rule import/no-relative-parent-imports should be what I am looking for. However, when I turn the rule on, all of my imports that are path rewrites in my tsconfig file report errors. See image below.
I have the following tsconfig.json
...
"baseUrl": ".",
"paths": {
"@commons/*": ["./commons/src/*"]
},
...
And the following eslintrc.js
...
"import/no-relative-parent-imports": ["warn"],
...
"settings": {
"import/resolver": {
"typescript": {},
}
}
...
When I log out the input before the error is reported here, I see the following paths getting reported:
../../types.ts
../../types.ts { id: 'import/no-relative-parent-imports',
It seems as though the typescript import/resolver is translating the paths before they are applied to this eslint check. Is there a way that I can configure my eslint to work with this use case? or is this not yet possible