Skip to content
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

Fix relative path of glob patterns when config is provided via the --config CLI option #5769

Open
akijoey opened this issue Dec 10, 2021 · 2 comments
Labels
status: needs discussion triage needs further discussion

Comments

@akijoey
Copy link

akijoey commented Dec 10, 2021

What is the problem you're trying to solve?

Following on #5604 (comment).

I think the glob patterns should be relative to the current working directory when config is provided via the --config CLI option.

Just like ESLint.

What solution would you like to see?

If a config is provided via the --config CLI option, the glob patterns in the config are relative to the current working directory rather than the base directory of the given config.

@jeddy3 jeddy3 added the status: needs discussion triage needs further discussion label Dec 18, 2021
@0liver
Copy link

0liver commented Mar 28, 2022

Absolutely! 😁

@jeddy3
Copy link
Member

jeddy3 commented Mar 28, 2022

I assume changing the default behaviour would be a breaking change? It's unlikely we'll do a major release any time soon, as they are painful for the community, but we could an option to trigger this behaviour (and then make it the default in the next major release). Something like --use-cwd?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: needs discussion triage needs further discussion
Development

No branches or pull requests

3 participants