Rule deprecation request #894
Comments
|
Is there some major version planned? (v3 maybe? :D) I could add a PR for this... |
|
We plan to make the next release a major version 👍 |
|
Svelte 5 supports Svelte4 features, therefore I think we can remove these rules in Svelte6 or 7. |
|
Ok, I'll make a PR. Let's deprecate the rules for now and remove them some time in the future (presumably after Svelte removes the deprecated features). I think it would be a good idea to review the recommended config for a new major version anyway. (Maybe add some new rules as well?) But I'll remove any deprecated rules from it. As an aside, I am looking into the three |
|
Actually, |
Uh oh!
There was an error while loading. Please reload this page.
Hi, I'm starting to update my projects to Svelte v5 and noticed that some of the rules I added were no longer relevant or outright incorrect. While at it, I went over all rules and I propose to deprecate the following ones (and eventually remove them once Svelte does so):
svelte/no-dupe-on-directives- duplicate directives now cause an error in Svelte itself, no need for a lint rule.svelte/no-dynamic-slot-name- slots are deprecated and snippets can't have a dynamic name afaiksvelte/no-reactive-reassign- Reactive statements are deprecatedsvelte/no-immutable-reactive-statements- Reactive statements are deprecatedsvelte/no-reactive-functions- Reactive statements are deprecatedsvelte/no-reactive-literals- Reactive statements are deprecatedsvelte/require-event-dispatcher-types- Events are deprecatedsvelte/experimental-require-slot-types- Slots are deprecated (chore: executesvelte/experimental-require-slot-typesonly on Svelte 3 and 4 #1005)svelte/experimental-require-strict-events- Events are deprecated and thestrictEventsattribute is removed outright in Svelte v5svelte/no-not-function-handler- Callbacks are regular props in Svelte 5 and thus are checked by TS.The text was updated successfully, but these errors were encountered: