You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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 :-)
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
The text was updated successfully, but these errors were encountered: