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

Allow override of some paths #6

Open
3 tasks done
joshbmarshall opened this issue Dec 10, 2023 · 2 comments
Open
3 tasks done

Allow override of some paths #6

joshbmarshall opened this issue Dec 10, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@joshbmarshall
Copy link

Clear and concise description of the problem

I have some vitesse projects where there is common code I keep in a separate git repository. So I have that as a subfolder of the projects and git clone there.

So that folder is in the .gitignore file as I wasn't going to add it as a submodule.

Because it's in the .gitignore file it's not running eslint on that common code.

Suggested solution

Would be great if we could somehow configure an override to allow some paths so they don't get ignored even though they are in the gitignore file

Alternative

I've currently disabled gitignore being used in the eslint.config.js but that means having to explicitly enter the paths to ignore and missing out on the goodness :)

Also considered using the common files as a git submodule but it comes with other complexities and git noise on the parent as it's the common repository that has the most dev activity.

Additional context

No response

Validations

@joshbmarshall joshbmarshall added the enhancement New feature or request label Dec 10, 2023
@antfu
Copy link
Owner

antfu commented Dec 11, 2023

How would you like to see the API? A custom filter function allowing you to decided programmatically?

@joshbmarshall
Copy link
Author

In reality for me it would just be hard-coded configuration. Although a function may work well for other developers who have more complex requirements than I do.

To be honest I wasn't wanting to dictate how it should be done - you've got a better idea on how the code all fits together and I'm more than happy to follow your guidance :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants