import-js/eslint-plugin-import
Auf GitHub ansehenno-restricted-paths - absolute path expected where relative path is provided
Open
#1.890 geöffnet am 24. Aug. 2020
help wanted
Repository-Metriken
- Stars
- (4.946 Stars)
- PR-Merge-Metriken
- (Durchschn. Merge 5T 21h) (9 gemergte PRs in 30 T)
Beschreibung
I am having trouble with the configuration for this rule and believe there is a bug in the way paths are resolved
// see https://github.com/benmosher/eslint-plugin-import/blob/master/src/rules/no-restricted-paths.js#L72
// it returns a relative path, are we sure thats what we want?
const absoluteImportPath = resolve(importPath, context)
Here we use resolve which comes from utils/resolve and it returns a relative path
should we be using path.resolve to return an absolute path instead? I am happy to open a PR with the change once confirmed
to be clear the change I am proposing is
- const absoluteImportPath = resolve(basePath, context)
+ const absoluteImportPath = path.resolve(basePath, importPath);