Skip to content

Move from internal expect rule to eslint-plugin-expect-type #858

@JoshuaKGoldberg

Description

@JoshuaKGoldberg

#843 migrated the old TSLint Expect rule to an ESLint rule (🥳!). Great!

There exists a community plugin for roughly the same area of functionality already: https://github.com/JoshuaKGoldberg/eslint-plugin-expect-type 1. It would be great if we could use the standard plugin instead. That way bugfixes + features from DT usage can help other community members, and vice versa.

Proposal:

  1. For each bug or feature that is better in this repo, we can file a corresponding issue on eslint-plugin-expect-type
  2. Once those are all fixed up, move to using the external plugin

Per later comments, tracking issues in eslint-plugin-expect-type for missing features:

Footnotes

  1. I do feel a bit weird promoting a package with my name on it. If it helps, I didn't create it - just took over maintenance when the previous maintainer didn't have time. If there's a better alternative to eslint-plugin-expect-type that'd be great too!

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