Skip to content

[dup] Sometimes, settings are ignored due to patched Linter.prototype.verify never being called #80

Closed
@CherryDT

Description

@CherryDT

I'm facing a strange issue. I have an .eslintrc.js which sets 'svelte3/ignore-styles': () => true, but it seems that when I open the project in VSCode, I have a random chance for it to work or fail (with "fail" meaning that it shows warnings about SCSS stuff that it shouldn't lint in the first place due to ignore-styles).

I have added some console.log statements to eslint-plugin-svelte3/index.js and it seems that in the "failing" case, the overwritten function Linter.prototype.verify never gets called, and therefore processor_options.ignore_styles never gets set with the function I defined.

When looking in the VSCode "ESLint" output console, I can in any case see a log statement being executed at the start of your index.js and then at the start of preprocess with my code, but in the failing case, I don't see any log statements executed inside Linter.prototype.verify nor inside the if (processor_options.ignore_styles) condition, while in the successful case, I see those run as well.

If it fails, what I do is reloading the VSCode window as often as required to see the log statement inside the Linter.prototype.verify override being executed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions