stylelint.validate in README doesn’t match with that in v1.0.0 Breaking change

[1zumii]

README/Extension Settings

stylelint.validate

Type: string[]
Default: ["css","postcss"]
An array of language identifiers specifying which files to validate.

v1.0.0 changelog/Breaking changes

Validation and completion now only works for documents with language identifiers css, less, and postcss by default.

less is not set by default

[adalinesimonian]

Good catch! Updated the readme in 4464251.

[1zumii]

but my vscode can’t lint less file in v1.0.0, until i set stylelint.validate to [css, less, postcss]. so i think less is not default language

[adalinesimonian]

Looks like there's a mistake in the extension: all three languages are correctly specified in the server, but Less is missing from the extension manifest. I'll push up a patch update in a moment. Thank you again!

[adalinesimonian]

@izumiiAoba I just pushed up v1.0.1, which should fix this problem. If it doesn't, let me know and I'll be happy to help!

[1zumii]

it work nice, thanks a lot 😎

[jeddy3]

@adalinesimonian Stylelint doesn't support Less out-of-the-box (a custom syntax is needed). Only CSS (and PostCSS because it's CSS-compatible) are. So, I believe the validate defaults were correct and it was the changelog and introduction in the README that were wrong.

Sorry that I missed this the first time around.

[adalinesimonian]

@jeddy3 Huh! I wonder where Less snuck in, then. When I originally threw Less into the defaults, I was certain I had seen something about the defaults needing to be CSS, Less, and PostCSS, which is why I kept Less in the server defaults when preparing for v1/14. However, I went back and pulled up #233 and I don't see any mention of Less, either now or in a past edit of a comment. So I'm honestly not sure where it came from.

So should we pull it out of defaults, push out another patch, regretfully inform our bug-reporting friend here that we goofed up?

[jeddy3]

So should we pull it out of defaults, push out another patch, regretfully inform our bug-reporting friend here that we goofed up?

Yes, I think so.