-
Notifications
You must be signed in to change notification settings - Fork 14
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
Dont work with Overrides? #9
Comments
Interesting use-case, there currently isn't an option for that. We don't hook into the eslint's official plugin api's (there is no api for us to hook into) so we run as a post |
My goal is to make "warn" all the ESLint rules inside a specific directory, because this directory have a "legacy" code base. And I don't want to disable the rules, but break only if we have Errors outside the "legacy" code base. |
Not sure if I should create a new issue... It's about using this plugin in editor only and fail in Git hook or CI. In the editor, the developer plays with the code which can produce eslint errors. To avoid that annoying behavior, the plugin only-warn is great. But for the CI/Git I would handle all as error. Or all just fail on all warnings. In best case the developer should be stopped during commit process. We already use husky/lint-staged ... Any idea? |
@infacto I think that you will need to create two |
Late but for those who are interested: Add parameter |
I'm trying to configure "only-warn" for just one directory in my project, using override: https://eslint.org/docs/latest/user-guide/configuring/configuration-files#configuration-based-on-glob-patterns
But, all files outside
src/legacy
are parsed with only-warn too. 😢Is there any option for that?
The text was updated successfully, but these errors were encountered: