Fix multi-line double-slash command comments

[jeddy3]

Refs: #4942 (comment) & #5346 (comment)

This issue only impacts users who are using Less and multi-line double-slash command comments, e.g.:

// stylelint-disable color-hex-case
// --
// description

a {color: #FFF; }

I doubt many, if any, users do this as Less isn't popular and support for multi-line double-slash command comments is a relatively new feature. As the workaround is to simply switch to /* style comments for these multi-line commands, I'd say this is a low priority. I'll add it to the 14.0.0 umbrella issue in case it does impact someone and they want to pick it up, but I don't see it as a blocker to releasing.

[nwalters512]

Wanted to add a +1 to this. We use a lot of such comments, and we started seeing Stylelint report issues in really weird places. For instance, a block of // comments in the middle of a file caused a lint error at the end of the file to be reported on a token in the middle of the comment. Here's a stripped-down version of that file illustrating the issue:

I finally managed to figure out that the common link between all files with weird errors was the use of multi-line // comments and trace it back to this GitHub issues. As you pointed out, one can work around this by switching to /*-style comments, but it was a reallllly confusing 30 minutes spent banging my head against the table until I figured out that that's what I had to do to resolve this.

EDIT: this may be unrelated to this issue, looks like this is specifically about commands and possibly only applies to the upcoming v14. Digging into this more - will file another issue if needed.

SECOND EDIT: I'm pretty confident this is a separate issue. I submitted a bug report in #5438.

[jeddy3]

EDIT: this may be unrelated to this issue, looks like this is specifically about commands and possibly only applies to the upcoming v14. Digging into this more - will file another issue if needed.
SECOND EDIT: I'm pretty confident this is a separate issue. I submitted a bug report in #5438.

Thanks for submitting the bug report. You're right that it's a separate issue. This issue specifically relates to a regression in the behaviour of multi-line double-slash command comments introduced by the migration to PostCSS@8 for the upcoming release.

[github-actions]

This issue is older than one month. Please ask before opening a pull request, as it may no longer be relevant.