We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Coming from dividab/tsconfig-paths#91, tsconfigPaths.loadConfig(path) accepts a file path too not only a directory.
tsconfigPaths.loadConfig(path)
I think the directory option should be renamed to something more descriptive. I have 2 alternatives in mind:
directory
tsconfigPath
project
@typescript-eslint/parser
parserOptions.project
This will be a breaking change!
The text was updated successfully, but these errors were encountered:
Let's waiting for the original issue first.
Sorry, something went wrong.
The conclusion of the original issue is that @typescript-eslint/parser will stick to using project. Do we want to change directory to project?
a662fc1
Successfully merging a pull request may close this issue.
Coming from dividab/tsconfig-paths#91,
tsconfigPaths.loadConfig(path)
accepts a file path too not only a directory.I think the
directory
option should be renamed to something more descriptive. I have 2 alternatives in mind:tsconfigPath
project
- will keep things consistent with@typescript-eslint/parser
(parserOptions.project
) - but it's in no way as descriptive astsconfigPath
This will be a breaking change!
The text was updated successfully, but these errors were encountered: