-
-
Notifications
You must be signed in to change notification settings - Fork 8
How to set options.rulePaths or --rulesdir #68
Comments
You can go to Project > Project Settings…, find ESLint in the Extensions section on the side, then set the "Path to ESLint configuration". If you'd prefer a global setting, look in Extensions > Extension Library…, find ESLint, then go to the Preferences tab to find a global version of the same setting. |
I might be misunderstanding but I still want ESLint to use the project |
Ah sorry, my misunderstanding. I assumed you were talking about configuration files 🤦🏻♂️ |
Nova 4 has a new feature I've been hoping for that might help with this. I can now add preferences that are arrays of paths. I'm thinking about adding a preference for "Additional eslint arguments" that you can use to set things like this. |
nova-eslint/ESLint.novaextension/extension.json Lines 60 to 64 in 6a2955d
|
#75 adds a config option for adding custom rules dirs. It appears there's a Nova bug preventing the preference from appearing globally when I restrict it to folders, but the workspace preference seems to work file. I'd appreciate someone trying it out locally before I merge and publish, since I don't usually use custom rules directories. |
* Add support for custom rules dirs Resolves #68 * Changelog * Add a bunch of test files for custom rules * Work around directory mangling issue * add link to eslint config docs * Improve console output when linting fails * changelog * format
Included in release v1.7.0 |
Our project has some rules we created and they are stored in a specific location.
I need a way to provide this path through either the options object or eslint arguments.
Can this be accomplished using this plugin?
The text was updated successfully, but these errors were encountered: