Skip to content

Rule deprecation request #894

@marekdedic

Description

@marekdedic

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 afaik
  • svelte/no-reactive-reassign - Reactive statements are deprecated
  • svelte/no-immutable-reactive-statements - Reactive statements are deprecated
  • svelte/no-reactive-functions - Reactive statements are deprecated
  • svelte/no-reactive-literals - Reactive statements are deprecated
  • svelte/require-event-dispatcher-types - Events are deprecated
  • svelte/experimental-require-slot-types - Slots are deprecated (chore: execute svelte/experimental-require-slot-types only on Svelte 3 and 4 #1005)
  • svelte/experimental-require-strict-events - Events are deprecated and the strictEvents attribute is removed outright in Svelte v5
  • svelte/no-not-function-handler - Callbacks are regular props in Svelte 5 and thus are checked by TS.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy