You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the recent edition of a rule that uses the parsed styles (#489), this rule in fact doesn't produce any errors if the styles cannot be parsed (either they're invalid, or svelte-eslint-parser cannot parse the used style language)
Description
I propose a rule that would produce a warning in either of these 2 cases (parse error / unknown language). This would guarantee that rules using styles (currently only no-unused-class-name) work correctly. There's also a minor overlap with the block-lang rule, but I think this is OK
I have a question.
Is this not detected by the preprocessor or something?
I thought that the preprocessor already has a parser such as SCSS or LESS etc, so if it failed to parse it would get some kind of error.
Some of it may as well be detected by the preprocessor, but svelte-eslint-parser for example can't read LESS (yet ;) ), so it would be useful to know that rules depending on style parsing are turned off in this case
Motivation
With the recent edition of a rule that uses the parsed styles (#489), this rule in fact doesn't produce any errors if the styles cannot be parsed (either they're invalid, or
svelte-eslint-parser
cannot parse the used style language)Description
I propose a rule that would produce a warning in either of these 2 cases (parse error / unknown language). This would guarantee that rules using styles (currently only
no-unused-class-name
) work correctly. There's also a minor overlap with theblock-lang
rule, but I think this is OKExamples
Additional comments
No response
The text was updated successfully, but these errors were encountered: