Skip to content

docs(parser): mention that relative paths rely on cwd #1576

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

Merged
merged 1 commit into from
Feb 10, 2020

Conversation

aryzing
Copy link
Contributor

@aryzing aryzing commented Feb 7, 2020

It was not clear that relative paths rely on the cwd. For example, a valid alternative interpretation could be that relative paths rely on the location of the eslintconfig file.

This change clarifies how the parserOptions.project relative paths are interpreted, and ties it in nicely with the existing recommendation to look at the tsconfigRootDir setting.

@typescript-eslint
Copy link
Contributor

Thanks for the PR, @aryzing!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!


🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day.

@bradzacher bradzacher added the documentation Documentation ("docs") that needs adding/updating label Feb 7, 2020
@armano2 armano2 changed the title Mention that relative paths rely on cwd docs(parser): mention that relative paths rely on cwd Feb 10, 2020
@bradzacher bradzacher merged commit 58182fe into typescript-eslint:master Feb 10, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Documentation ("docs") that needs adding/updating
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants