stylelint showing CssSyntaxError on markdown files

Created on 12 Mar 2018  ·  3Comments  ·  Source: stylelint/stylelint

Describe the issue. Is it a bug or a feature request (new rule, new option, etc.)?

Today I noticed that stylelint in VSCode started to show errors inside markdown files. I think that's a bug …

Which rule, if any, is this issue related to?

"Missing semicolon (CssSyntaxError)"

What CSS is needed to reproduce this issue?

Well not CSS in this case but a markdown file with some front matter on the top. E.g.:

layout: faq
[more stuff]
---

What stylelint configuration is needed to reproduce this issue?

I'm using this in my package.json:

"stylelint": {
  "extends": "stylelint-config-recommended-scss"
}

Which version of stylelint are you using?

9.1.1

How are you running stylelint: CLI, PostCSS plugin, Node API?

VSCode Plugin version 0.34.0

Does your issue relate to non-standard syntax (e.g. SCSS, nesting, etc.)?

Well ... I guess. Since it's in markdown files :)

What did you expect to happen?

That no linting would happen at all..

What actually happened (e.g. what warnings or errors you are getting)?

For example this:

Missed semicolon (CssSyntaxError)
needs discussion

Most helpful comment

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

It looks like this problem was raised in VSCode extension issue tracker and the author of that extension kindly raised an issue in postcss-html (a dependency of stylelint). The author of that package, in turn, fixed the issue. The chain broke down because we haven't released a new version of stylelint yet (mainly because the problem wasn't on our radar until you raised this issue).

@stylelint/core If no one has any objections, I can do a patch release tonight or tomorrow with the new postcss-html dependency.

All 3 comments

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

It looks like this problem was raised in VSCode extension issue tracker and the author of that extension kindly raised an issue in postcss-html (a dependency of stylelint). The author of that package, in turn, fixed the issue. The chain broke down because we haven't released a new version of stylelint yet (mainly because the problem wasn't on our radar until you raised this issue).

@stylelint/core If no one has any objections, I can do a patch release tonight or tomorrow with the new postcss-html dependency.

Woohoooo Sounds Great 👍🏼

On 12. Mar 2018, at 20:54, Richard Hallows notifications@github.com wrote:

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

It looks like this problem was raised in VSCode extension issue tracker and the author of that extension kindly raised an issue in postcss-html (a dependency of stylelint). The author of that package, in turn, fixed the issue. The chain broke down because we haven't released a new version of stylelint yet (mainly because the problem wasn't on our radar until you raised this issue).

@stylelint/core If no one has any objections, I can do a patch release tonight or tomorrow with the new postcss-html dependency.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Released as 9.1.2.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

bdefore picture bdefore  ·  3Comments

devsnice picture devsnice  ·  3Comments

jeddy3 picture jeddy3  ·  3Comments

Havunen picture Havunen  ·  3Comments

jonathantneal picture jonathantneal  ·  3Comments