Inform the user that documents containing disable comments can't be autofixed about vscode-stylelint HOT 3 OPEN

@kanlukasz Thanks for the report and for using the template.

This is a known limitation of the autofix feature that we need help to fix. At the moment the autofix feature doesn't respect disable comments, so stylelint no longer attempts to fix sources that contain them.

However, this issue makes me think we should surface an info-severity message either in stylelint itself or within this extension letting the user know that files containing disable comments can not currently be autofixed.

from vscode-stylelint.

@jeddy3 Has this changed upstream since this issue was opened? First thought off the top of my head is that it may make sense for the message to come from Stylelint itself and for the extension to bubble it up to the user.

from vscode-stylelint.

Has this changed upstream since this issue was opened?

Nope.

First thought off the top of my head is that it may make sense for the message to come from Stylelint itself and for the extension to bubble it up to the user.

Sounds good.

from vscode-stylelint.