[Feature]: Provide a command to restart the stylelint extension

[stefan-toubia]

What problem does this feature solve?

Config changes are not always picked up by the extension automatically. This leads to some stale lint errors without an easy way to refresh. Many other extensions, such as the ESLint extension, provide a command to restart the server for the same reason.

How does this feature solve the problem?

This gives users a way to manually refresh lint errors.

What are some alternatives to this feature?

Better automatic reloading for config files.

Code of Conduct

• [X] I agree to follow vscode-stylelint's Code of Conduct

[ota-meshi]

Thank you for posting the issue. It's already planned. #332

[stefan-toubia]

Horay. But that was completed almost a year ago, what's the hold up?

[ota-meshi]

I think it will be released sooner when @adalinesimonian comes back. I'm not sure otherwise.

[adalinesimonian]

Hello, folks! I've been gone for a long while because of some crazy stuff that's been going on in my life. But, good news: my job is letting me work on Fridays on open source commitments — on the clock! As long as there are no fires to put out, of course. This week I'm quite busy, but starting next week you will see me active on Fridays. I will take a look at this ticket and others next week. :)

[adalinesimonian]

Just an update, working on some upstream updates and fixes to jest-runner-vscode to get test suites in here ready for new vscode versions and test failures resolved.

[GNRSN]

+1

We're in the process of adopting stylint in a large monorepo and found this to be a pain-point while itrerating on rules and ensuring consistency between sub-modules. Eagerly awaiting this update 😄