Closed ryoppippi closed 1 month ago
I had a discussion with @baseballyama and svelte/valid-compile
is not needed in my use case
So I close this. Thanks!
@ota-meshi As Svelte is a compiler, it may not compile correctly without a pre-processor. <enhanced:img>
is an example. How should this be addressed? My opinion is that we could deprecate this rule in the next major version release, but I'm sure you have a better idea.
In my opinion, I think the valid-compile
rule is unnecessary and can be deprecated, because the same errors can be displayed more accurately if you use Svelte compilation instead of ESLint.
The rule was created for the purpose of displaying the same errors as eslint-plugin-svelte3
. (eslint-plugin-svelte3
displayed Svelte compilation errors as lint errors.)
However, we still need tasks that compile with Svelte because of the no-unused-svelte-ignore
rule. I don't know yet if the preprocessor affects it.
https://sveltejs.github.io/eslint-plugin-svelte/rules/no-unused-svelte-ignore/
Before You File a Bug Report Please Confirm You Have Done The Following...
What version of ESLint are you using?
9.5.0
What version of
eslint-plugin-svelte
are you using?2.41.0
What did you do?
Configuration
``` 'svelte/valid-each-key': 'error', ```and got diagnostics like below:
What did you expect to happen?
When using
<img />
instead of<enhanced:img />
, it works fine.What actually happened?
Got weird diagnostics
Additional comments
https://kit.svelte.dev/docs/images