Allow for different configuration files

I’m having trouble getting this plugin to work due to the config file location being specifically set in linter.py. I’m currently configuring my setup to use stylelint.config.js rather than .stylelintrc since I need to use JS object syntax rather than JSON. However, in linter.py, the config file is specifically set to .stylelintrc, which means it doesn’t work for my setup. Ideally it would be nice to move to NodeLinter, since this is handled automatically, but I saw #19 which explained the reasoning for keeping the current plugin architecture, using stylelint_wrapper.js, but it’s pretty inflexible and doesn’t allow for the varied configuration files that the CLI allows for.

Can you update the stylelint_wrapper.js to not pass a specific config file and let it search relative to the CWD of the file being linted when using the CLI, or can you switch to NodeLinter?

[jo-sm]

@chrishoage see https://github.com/SublimeLinter/SublimeLinter3/issues/483. I made an issue for stylelint_d, which is long-running process for stylelint that I made for Sublime, which also accepts non .stylelintrc configs.

[jo-sm]

Yeah I agree – although ideally it would be as simple as seeing if they have the CLI, and if they do, just use NodeLinter, otherwise, run the old wrapper. I may fork this and write my own version of this that also supports a running node process (Node startup on my computer is sloooooow…), see SublimeLinter-contrib-eslint_d for an example of what I’m talking about. Even for a simple file, on my computer, it can take around 1 second for the linting to complete…