Skip to content

[no-duplicate-imports] deprecate rule in favour of import/no-duplicates #4238

Closed
@bradzacher

Description

@bradzacher

Separating out from #4225 (comment)

In #2609 we added an extension rule for the core no-duplicate-imports. In hindsight - this wasn't a great idea because there already exists an even better rule in the ecosystem - import/no-duplicates.

Instead of us attempting to maintain a competing rule we should instead deprecated our version of the rule and point users at the eslint-plugin-import rule instead.

Similar to camelcase - we can maintain a markdown doc which points users to the better rule.

Metadata

Metadata

Assignees

No one assigned

    Labels

    accepting prsGo ahead, send a pull request that resolves this issuebreaking changeThis change will require a new major version to be releasedpackage: eslint-pluginIssues related to @typescript-eslint/eslint-plugin

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions