-
Notifications
You must be signed in to change notification settings - Fork 37
Instructions slightly unclear #390
Comments
I also would love a little more direction here, I've added an indentation override to my I tried it two ways: ...
"version": "4.2.0",
"stylelint": {
"indentation": "tab",
"rules": {
"indentation": "tab"
}
}
} An example |
This package is meant to be a wrapper around |
Am I misunderstanding then that you can't extend the standard config built into stylelint (assuming |
The "Use Standard" option enables the |
Thanks! |
That's not necessarily shared unless all of our projects are in one place (which most of the time they're not). I've gone through the style-lint documentation but I can't seem to find anyone who's been able to set up a shared extension of the standard rules. |
There are several hundred "shared extensions to the standard rules" out there, since virtually everyone starts with Ideally your linting configuration should live with the project, since that way everyone working on the project gets the same configuration for style and checking, even if the "other people" working on it are just you in the future. If placing a configuration file in a parent directory to your projects isn't going to work for you, your only other option is to modify the code of this package, but as I'm a firm believer in having the project configuration stored with the project I'm not going to provide any assistance with that. |
Add a
stylelint
section in yourpackage.json.
I've tried modifying the package.json (belonging to linter-stylelint) but when I attempt to reload Atom, it fails to load the package. I feel like I may be doing this wrong, would you mind showing me an example of the implementation?
I am very confused rn. Am I even modifying the right file?
Is this only for node package developers?
I'm just looking for a way to alter the global settings so I can share config settings between projects without having to continuously make .stylelintrc.json in every single project.
The text was updated successfully, but these errors were encountered: